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

On Tue, Jan 7, 2014 at 3:31 PM, Simon Sapin <> 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