W3C home > Mailing lists > Public > www-style@w3.org > January 2014

Re: [css-syntax] CR publication, Encodings and @charset

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 7 Jan 2014 17:13:59 -0800
Message-ID: <CAAWBYDATXOFQHExfT+4P=ch=M-RKa6tgmbpC_OuJ2NbZaK-Vug@mail.gmail.com>
To: Simon Sapin <simon.sapin@exyr.org>
Cc: www-style <www-style@w3.org>, WWW International <www-international@w3.org>
On Tue, Jan 7, 2014 at 3:31 PM, Simon Sapin <simon.sapin@exyr.org> wrote:
>> There is also mention in the section on the @charset rule that the
>> byte sequence will "spell out something else entirely" if the
>> character encoding isn't ASCII-compatible. Perhaps the text should be
>> explicit: the only non-ASCII-compatible encodings that can be used
>> for a CSS stylesheet are UTF-16 and its endian friends LE and BE.
> I removed that mention, as it was not useful in explaining the difference
> between the @charset at-rule and byte pattern.

This doesn't quite address their feedback.  As currently written,
Syntax doesn't allow UTF-16 *either*, unless you use a BOM for the
Encoding Standard to pick up.  You definitely can't use @charset to
specify utf-16, at least as specified.

Received on Wednesday, 8 January 2014 01:14:47 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:36 UTC