W3C home > Mailing lists > Public > public-html@w3.org > August 2009

Re: HTML5 Issue 11 (encoding detection): I18N WG response...

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 20 Aug 2009 00:33:59 -0700
Cc: Henri Sivonen <hsivonen@iki.fi>, "Phillips, Addison" <addison@amazon.com>, "public-html@w3.org" <public-html@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-id: <B578F189-D8A7-4A5F-93B7-B5668BDEAD88@apple.com>
To: Andrew Cunningham <andrewc@vicnet.net.au>

On Aug 20, 2009, at 12:29 AM, Andrew Cunningham wrote:

>
>
> Henri Sivonen wrote:
>
>> On Aug 20, 2009, at 10:15, Phillips, Addison wrote:
>>
>>> Setting UTF-8 as a default may produce the dreaded "black  
>>> diamonds" on the screen. But so too choosing the wrong encoding at  
>>> (relative) random.
>>
>> The thing is, the indication of the user's locale is not random  
>> data on a personal computer. It's works rather well when people  
>> read Web pages in their local language and in English, which is the  
>> common thing to do.
>>
> in that case you'd need to implement language specific encoding fall  
> backs rather than geographical fullbacks.
>

Many browsers in fact do this based on the user's primary language  
rather than by geography.

Regards,
Maciej
Received on Thursday, 20 August 2009 07:34:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:44 GMT