W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2009

Re: [selectors-api] Selectors API I18N Review...

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 28 Jan 2009 20:38:10 -0800
Message-ID: <498132B2.6010804@inkedblade.net>
To: "Phillips, Addison" <addison@amazon.com>
CC: "public-webapps@w3.org" <public-webapps@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, www-style@w3.org

Phillips, Addison wrote:
> Dear Webapps WG,
> 
> I am writing on behalf of the I18N Core WG who discussed the Selectors
> API WD in our call of 3 December [1].
> 
> We reviewed the Selectors API working draft. In reviewing this draft,
> we did not find any internationalization issues in the text of the
> document. However, we would like to point out that the CSS3 Selectors
> themselves have outstanding internationalization comments not addressed
> in the current version of that document [4] and which would (we think)
> impact anyone who were to implement the Selectors API. Our comments on
> CSS3 Selectors are located at [2]. We also note that Unicode Normalization
> is not treated anywhere in this draft or in CSS3 Selectors.
> ...
> [1] http://www.w3.org/2008/12/03-core-minutes.html
> [2] http://www.w3.org/International/reviews/0601-css3-selectors/ 
> [3] http://lists.w3.org/Archives/Member/member-i18n-core/2008Dec/0006.html 
> [4] http://www.w3.org/TR/css3-selectors/ aka http://www.w3.org/TR/2005/WD-css3-selectors-20051215 

I have reviewed all of your outstanding comments on Selectors, and with
the exception of a request for a bidi example [1], all of them have been
dealt with in the upcoming draft [2].

As far as I know (and perhaps my memory does not go back far enough, I
have only been in the WG since 2004), the CSS Working Group has no record
of the I18n Working Group raising an issue with regards to Unicode
Normalization in any of our specs. If the I18nWG would like us to address
this issue, please raise an issue against /our/ specs, preferably with a
recommended solution. Such an issue would potentially affect the following
specs at least:
   [CSS21]          CSS2.1
   [css3-namespace] CSS Namespaces
   [css3-selectors] Selectors Level 3
   [css3-content]   CSS Generated and Replaced Content Level 3
   [css3-page]      CSS Paged Media Level 3
   [css3-gcpm]      CSS Generated Content for Paged Media Level 3

I will note that a previous version of the Selectors module included a
paragraph on Unicode normalization in the Conformance Requirements section:
   http://www.w3.org/TR/2001/CR-css3-selectors-20011113/#Conformance
which appears to have been removed in response to comments as described here:
   http://lists.w3.org/Archives/Member/w3c-css-wg/2005OctDec/0158.html

[1] http://lists.w3.org/Archives/Public/public-i18n-core/2006JanMar/0049.html
[2] http://dev.w3.org/csswg/selectors3

~fantasai
Received on Thursday, 29 January 2009 04:39:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 January 2009 04:39:03 GMT