Bug 93985

Summary: -webkit-locale should be inferred from system language
Product: WebKit Reporter: Alexey Proskuryakov <ap>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: efidler, esprehn, falken, jshin
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 10874    

Description Alexey Proskuryakov 2012-08-14 09:47:01 PDT
Consider the following HTML document:

<p>John said <q>Mary said <q>blah</q> to me.</q></p>

All these quotes will be displayed as ASCII ones, which is not right.

I think that we should use system language as the last fallback for document language, as this would be correct more often than not. Of course, lang attribute or HTTP headers would still have precedence.
Comment 1 Alexey Proskuryakov 2013-02-20 15:19:29 PST
Comment 2 Matt Falkenhagen 2013-03-07 22:21:56 PST
A related Chromium bug is https://code.google.com/p/chromium/issues/detail?id=179331
Comment 3 Alexey Proskuryakov 2013-03-07 23:08:02 PST
This should be pretty easy to do, we already track system language in WebCore (on Mac).
Comment 4 Alexey Proskuryakov 2013-03-07 23:08:53 PST
(and many other WebKit based browsers have the language user configurable)
Comment 5 Jungshik Shin 2013-03-19 15:15:25 PDT
bug 18085 is also related. The precedence order would be 

1. explicit lang/xml:lang (and Content-Language)
2. charset to lang mapping
3. OS/System language (or UI langauge if UI language is different from OS/System language)
Comment 6 Jungshik Shin 2013-03-19 15:17:11 PDT
BTW, when we do step #2, we also have to take into account system/UI language to break the degeneracy (ISO-8859-1, windows-1252 : what to map to? 'en' is a good fallback, but if the system/UI language is French, 'fr' would be better).