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

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

From: Andrew Cunningham <andrewc@vicnet.net.au>
Date: Mon, 12 Oct 2009 23:02:36 +1000
Message-ID: <9472df0aa9c92e82db33d09bd5e3469c.squirrel@mail.vicnet.net.au>
To: "Maciej Stachowiak" <mjs@apple.com>
Cc: "Ian Hickson" <ian@hixie.ch>, "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>, Mark Davis ˜• <mark@macchiato.com>, "Henri Sivonen" <hsivonen@iki.fi>, "Martin_J=2E_D=FCrst" <duerst@it.aoyama.ac.jp>, "Phillips, Addison" <addison@amazon.com>, "Andrew Cunningham" <andrewc@vicnet.net.au>, "Richard Ishida" <ishida@w3.org>, "public-html@w3.org" <public-html@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, "Larry Masinter" <masinter@adobe.com>

On Mon, October 12, 2009 22:00, Maciej Stachowiak wrote:

> Mozilla's choices for these are publicly available. Safari (and I
> think other WebKit-based browsers, though I'm not positive) uses
> Windows-1252 as the default for everything. We believe this is a bad
> choice, however, for users in some locales (for example, Russian,
> Chinese and Japanese locales). Users in those locales often find they
> need to change the default.

I'd be curious to know what happens with south asian locales, esp since
most if not all legacy encodings aren't supported by web browsers.

and vietnamese is a difficult langauge, since there isn't any one dominant
legacy enncoding, would need soem sort of suto detect mechanism, assuming
web browsers actually supported all the key legacy encodings, which form
memory they don't.

> We're willing to converge on a specified behavior for this.
> Regards,
> Maciej

Andrew Cunningham
Research and Development Coordinator
State Library of Victoria

Received on Monday, 12 October 2009 13:03:13 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:52 UTC