W3C home > Mailing lists > Public > www-international@w3.org > October to December 2013

Re: Re: Guessing the fallback encoding from the top-level domain name before trying to guess from the browser localization

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Sat, 21 Dec 2013 14:35:40 +0100
To: Jungshik SHIN (신정식) <jshin1987@gmail.com>
Cc: Henri Sivonen <hsivonen@hsivonen.fi>, "www-international@w3.org" <www-international@w3.org>
Message-ID: <20131221143540974287.0535460e@xn--mlform-iua.no>
Henri Sivonen, Sat, 21 Dec 2013 14:16:41 +0200:
> On Fri, Dec 20, 2013 at 10:58 PM, Jungshik SHIN (신정식) wrote:

>> It is off by default. Even when it is on, it is only used in absence of an
>> explicit declaration either via http c-t header or meta tag. It never
>> overides the declared encoding.
> Cool. Why did you feel it was worthwhile to add an off-by-default
> feature like that--especially when WebKit already had code for
> Japanese sniffing and ap@apple seems to think that's enough? It looks
> pretty alarming to see a browser *add* to its content-based sniffing
> capability!
> For clarity: Is hamburger menu: Tools: Encoding: Auto Detect the UI 
> for this?

To Jungshik SHIN: Has this feature *always* been off-by-default? Or has 
Chrome, in the past, had it on-by-default? (According to my memory, 
there was a period when it was on by default.)

> Does this mean that any sort of content-based autodetection is off by
> default even for the Japanese localization of Chrome?
leif halvard silli
Received on Saturday, 21 December 2013 13:36:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:03 UTC