W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] [html5] r5258 - [e] (0) Some more references to UTF-8.

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 10 Aug 2010 10:11:25 -0700
Message-ID: <AANLkTin6Qb=TWuYBeD9mARbKxsvL2j0OV00v7DovQWy-@mail.gmail.com>
On Tue, Aug 10, 2010 at 4:53 AM, Leif Halvard Silli
<xn--mlform-iua at xn--mlform-iua.no> wrote:
> whatwg at whatwg.org, Mon, ?9 Aug 2010 18:16:12 -0700 (PDT):
>> Author: ianh
>> Date: 2010-08-09 18:16:10 -0700 (Mon, 09 Aug 2010)
>> New Revision: 5258
>
>> ? ?<p>Authors are encouraged to use UTF-8. Conformance checkers may
>> - ?advise authors against using legacy encodings.</p>
>> + ?advise authors against using legacy encodings. <a
>> href=#refsRFC3629>[RFC3629]</a></p>
>
> Could we replace 'legacy encodings' with a clearer wording - or
> eventually define what 'legacy encodings' mean? The current wording
> could give the impression that any encoding other than UTF-8 is a
> legacy encoding. But it is unclear whether that is actually what is
> meant.
>
> Specifically, it is not clear from the above whether conformance
> checkers may advice authors against using UTF-16, since UTF-16
> generally isn't associated with 'legacy encoding'.

That's precisely what's meant.  UTF-8 is the encoding of the web.  Any
and all other encodings are legacy encodings.

~TJ
Received on Tuesday, 10 August 2010 10:11:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:59 UTC