W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

Re: [css-syntax] ISSUE-329: @charset has no effect on stylesheet??

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 23 Jan 2014 12:27:35 -0800
Message-ID: <CAAWBYDD0STc=B=-p_Y+Dc0kJGWnCMMx8wQ-zKBf=rTM7j3ZdXA@mail.gmail.com>
To: Asmus Freytag <asmusf@ix.netcom.com>
Cc: Simon Sapin <simon.sapin@exyr.org>, "Phillips, Addison" <addison@lab126.com>, Anne van Kesteren <annevk@annevk.nl>, Richard Ishida <ishida@w3.org>, Zack Weinberg <zackw@panix.com>, www-style list <www-style@w3.org>, www International <www-international@w3.org>
On Thu, Jan 23, 2014 at 11:21 AM, Asmus Freytag <asmusf@ix.netcom.com> wrote:
> On 1/23/2014 10:18 AM, Tab Atkins Jr. wrote:
>> So, in sum:
>> 1. Nobody should be using @charset in the first place. We only retain
>> it for legacy purposes, and new stylesheets should just be done in
>> utf-8.
>> 2. There is a realistic concern that we're already under legacy
>> constraints to not loosen the syntax.
>> 3. CSS parsing allows for *far* more variation than just "more spaces
>> and either type of quote".
>> 4. UAs are very unlikely to implement the full flexibility of CSS
>> parsing just for encoding detection.
>> 5. If we specify only a subset of allowed variation, the original goal
>> of making encoding detection aligned with valid @charset rules is
>> still not satisfied.
>> For all these reasons, I strongly reject any proposal to change the
>> current specification regarding the strictness of the encoding
>> declaration syntax.
> Succinctly reasoned.
> Will the spec be written accordingly?

It already is written accordingly.  Unless you mean something more specific?

Received on Thursday, 23 January 2014 20:28:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:04 UTC