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

RE: CSS Syntax issues [I18N-ACTION-276]

From: Phillips, Addison <addison@lab126.com>
Date: Thu, 23 Jan 2014 17:06:39 +0000
To: Simon Sapin <simon.sapin@exyr.org>, "CSS WWW Style (www-style@w3.org)" <www-style@w3.org>
CC: www International <www-international@w3.org>
Message-ID: <7C0AF84C6D560544A17DDDEB68A9DFB517C82BD3@ex10-mbx-36009.ant.amazon.com>
Hi Simon,

The changes to the @charset section look good. Thank you for that. I will close the specific issues related to that wording.

I don't believe that the I18N WG is satisfied by the text in:


There is on-going discussion as recent as yesterday about our dissatisfaction with forbidding multiple spaces or the alternate use of single- or double-quotes (as would be consistent with the definition of <string> in CSS3 Syntax and thus the definition in the section on @charset). I (and possibly others) intend to reply specifically to the open thread under separate cover, so I won't do so here, except to say that I18N WG members feel that the overly restrictive syntax is a barrier that users will trip over rather than an aid to interoperability.



Addison Phillips
Globalization Architect (Amazon Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.

> -----Original Message-----
> From: Simon Sapin [mailto:simon.sapin@exyr.org]
> Sent: Thursday, January 23, 2014 8:50 AM
> To: Phillips, Addison; CSS WWW Style (www-style@w3.org)
> Cc: www International
> Subject: Re: CSS Syntax issues [I18N-ACTION-276]
> On 23/01/2014 07:40, Phillips, Addison wrote:
> > Dear CSS,
> >
> > As you probably noticed, we closed a number of issues that we had
> > raised that you addressed with a recent update. Thank you.
> >
> > In addition, we have three remaining issues open [1]. There is
> > on-going discussion of the substantive @charset issues. The remaining
> > issue, I18N-ISSUE-306, is a editorial issue related to how the byte
> > 0x22 and/or the character U+0022 is referred to in the section on
> > parsing @charset.
> >
> > Thanks (for I18N),
> >
> > Addison
> >
> > [1] https://www.w3.org/International/track/products/54

> Hi,
> I believe all three issues listed in [1] to be resolved, as the corresponding spec
> text has been rewritten in the Editor’s Draft to not include the problematic
> statements (such as "The @charset rule has not effect on stylesheets"), or
> otherwise clarify the intended meaning.
> The specifics are here:
> http://lists.w3.org/Archives/Public/www-style/2014Jan/0060.html

> If you believe this is not resolved, please point up which specific parts are still
> problematic in the Editor’s Draft.
> There is additionally a mailing-list discussion about changing the
> behavior of the @charset byte sequence (that provides an encoding hint)
> or the at-rule (that ends up in CSSOM), but this is a separate issue
> from what is listed in [1].
> --
> Simon Sapin
Received on Thursday, 23 January 2014 17:12:41 UTC

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