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

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

From: Asmus Freytag <asmusf@ix.netcom.com>
Date: Wed, 22 Jan 2014 13:09:47 -0800
Message-ID: <52E0339B.4070202@ix.netcom.com>
To: "Phillips, Addison" <addison@lab126.com>, Anne van Kesteren <annevk@annevk.nl>, Richard Ishida <ishida@w3.org>
CC: "Tab Atkins Jr." <jackalmage@gmail.com>, Zack Weinberg <zackw@panix.com>, www-style list <www-style@w3.org>, www International <www-international@w3.org>
On 1/22/2014 12:25 PM, Phillips, Addison wrote:
> The issue here is that CSS's normal syntax allows different whitespace and quote formation within the actual CSS of the file. But the character encoding declaration requires SPECIFIC space and quoting. That variation is not friendly to users of CSS, who expect that @charset is just a normal syntactic element of CSS, even if, in actuality, it is not. Since the byte munging involved is not remarkably difficult to describe or implement and since it will improve the likelihood that people "get it right" (let alone not breaking existing stylesheets that somehow get it wrong), why not specify @charset consistently with the rest of CSS? I'm fine with saying it has to come first, etc. for the reasons you cite.
seems weird to create a "gotcha" like this unless there's totally no 
alternative. The limitation on quotes and number of spaces strike me as 
not utterly not predictable to anyone who's not carefully studied just 
this aspect of CSS....

>> -----Original Message-----
>> From: annevankesteren@gmail.com [mailto:annevankesteren@gmail.com] On
>> Behalf Of Anne van Kesteren
>> Sent: Wednesday, January 22, 2014 11:35 AM
>> To: Richard Ishida
>> Cc: Tab Atkins Jr.; Zack Weinberg; www-style list; www International
>> Subject: Re: [css-syntax] ISSUE-329: @charset has no effect on stylesheet??
>> On Wed, Jan 22, 2014 at 11:11 AM, Richard Ishida <ishida@w3.org> wrote:
>>> PS: I'm curious, however, about why the parsing of the initial bytes
>>> is so draconian in requiring specific quotes and exactly one space.
>>> HTML5 doesn't require that, afaict.
>> Because we learn from our mistakes, somewhat. The way HTML does
>> encodings is terrible.
>> --
>> http://annevankesteren.nl/
Received on Wednesday, 22 January 2014 21:10:15 UTC

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