W3C home > Mailing lists > Public > www-style@w3.org > June 2011

RE: Unicode normalization in CSS [css3-namespace]

From: Phillips, Addison <addison@lab126.com>
Date: Wed, 22 Jun 2011 13:14:09 -0700
To: fantasai <fantasai.lists@inkedblade.net>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <131F80DEA635F044946897AFDA9AC3476A93BF68C9@EX-SEA31-D.ant.amazon.com>
The Internationalization WG believes that, while normalization could potentially affect namespaces, for the reason you mention below it is not likely to represent an important issue in this case. Therefore we have no objection to your resolution of this issue nor to your closing this issue and proceeding to publish CSS Namespaces.

We are preparing to ask TAG for a finding based on our current WG position regarding Unicode Normalization and this may have an effect on CSS (and other W3C) specs in the future.

Thank you for your WG's help.

Addison

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

Internationalization is not a feature.
It is an architecture.



> -----Original Message-----
> From: public-i18n-core-request@w3.org [mailto:public-i18n-core-
> request@w3.org] On Behalf Of fantasai
> Sent: Wednesday, June 22, 2011 11:13 AM
> To: public-i18n-core@w3.org; www-style@w3.org
> Subject: Re: Unicode normalization in CSS [css3-namespace]
> 
> On 04/07/2011 08:11 PM, fantasai wrote:
> > There was a very very very long thread on Unicode normalization in CSS
> > back in January/February of 2009. [...]
> 
> This is a formal response from the CSS Working Group with regards to CSS
> Namespaces CR <http://www.w3.org/TR/css3-namespace/> whose Disposition
> of Comments is here: <http://dev.w3.org/csswg/css3-namespace/issues-3>
> 
> The CSS Working Group believes this issue to be out-of-scope for Namespaces.
> We believe it needs to be addressed at a higher, W3C-wide level, and should be
> filed as an issue with the TAG. We are therefore closing this as out-of-scope for
> CSS Namespaces, which are internal to a single CSS file anyway and therefore
> least likely to present problems wrt normalization.
> 
> Please let us know if this resolution is acceptable to you.
> 
> ~fantasai

Received on Wednesday, 22 June 2011 20:14:45 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:41 GMT