- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 8 Jan 2014 09:17:46 +0000
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Simon Sapin <simon.sapin@exyr.org>, www-style <www-style@w3.org>, WWW International <www-international@w3.org>
On Wed, Jan 8, 2014 at 1:13 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > 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. And we should keep it that way :-) Just like <meta>, @charset should only work for ASCII-compatible encodings, which means encodings other than utf-16be and utf-16le (utf-16 as such is not a thing anymore per Encoding). -- http://annevankesteren.nl/
Received on Wednesday, 8 January 2014 09:18:19 UTC