On Sat, Feb 8, 2014 at 12:37 AM, Ian Hickson i...@hixie.ch wrote:
What have you learnt so far?
I've learned that I've misattributed the cause of high frequency of
character encoding menu usage in the case of the Traditional Chinese
localization. We've been shipping after the wrong fallback
On Sat, Feb 8, 2014 at 12:37 AM, Ian Hickson i...@hixie.ch wrote:
The correlation should be at least as high, as far as I can tell.
Logically, yes, for most parts of the world.
Or maybe a 50%/50% experiment
with that as the first 50% and the default coming from the TLD instead of
the UI
On Thu, 19 Dec 2013, Henri Sivonen wrote:
Considering that the encoding of the content browsed is not really a
function of the UI localization of the browser, though the two are often
correlated, I have developed a patch for Firefox to make the guess based
on the top-level domain name of
(Posted to whatwg and www-international but not cross-posted, because
cross-posting would be against the whatwg list rules.)
Currently, the main source of fallback encoding (the encoding used for
text/html and text/plain in the absence of a site-supplied encoding
label) is that the UI
