- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Sat, 1 Feb 2014 11:11:44 +0100
- To: Simon Sapin <simon.sapin@exyr.org>
- Cc: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, "Tab Atkins Jr." <jackalmage@gmail.com>, Zack Weinberg <zackw@panix.com>, Simon Pieters <simonp@opera.com>, www-style list <www-style@w3.org>, www International <www-international@w3.org>
Simon Sapin, Sat, 01 Feb 2014 08:39:25 +0100: > On 31/01/2014 06:17, Leif Halvard Silli wrote: >> Richard Ishida, Fri, 24 Jan 2014 18:23:56 +0000: >>> On 24/01/2014 17:06, Anne van Kesteren wrote: >> HTML(5) permits <meta charset="UTF-8"/> in XHTML, as long as it >> specifies "UTF-8". And it seems like not recommending @charset in CSS, >> except when it says "UTF-8", could be a similarly decent rule. > Tab recently added a note at the end of the section that I think > covers this scenario. > > http://dev.w3.org/csswg/css-syntax/#input-byte-stream >> If neither of these options are available, authors should begin the >> stylesheet with a UTF-8 BOM or the exact characters @charset >> "utf-8";. Cool. But I would recommend placing the string ”@charset "utf-8";” on a separate line, to avoid the dot at the end of the ”exact characters” … > Also, this sounds like a special enough case that we can afford to > teach people to use the exact byte sequence without relaxing its > syntax requirements. -- Leif Halvard Silli
Received on Saturday, 1 February 2014 10:12:14 UTC