Phillips, Addison wrote:
Assuming for a moment that CSS3 does not resolve the problem with
Unicode normalization in selectors, users of selectors-api will be
potentially surprised by the results in certain circumstances
involving denormalized selectors.
I have discussed this with my
Phillips, Addison wrote:
However, I18N feels that our two WGs can construct a useful,
informative, small, and relatively-painless bit of text to allow you
to proceed. Please let us know if you think this an appropriate way
to address this issue or if we can assist in any way to help you guys
.
It is an architecture.
-Original Message-
From: Lachlan Hunt [mailto:lachlan.h...@lachy.id.au]
Sent: Friday, January 30, 2009 3:16 PM
To: Phillips, Addison
Cc: public-webapps@w3.org; public-i18n-c...@w3.org
Subject: Re: [selectors-api] Selectors API I18N Review...
Phillips
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
Phillips, Addison wrote:
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,
...@w3.org
Subject: Re: [selectors-api] Selectors API I18N Review...
Phillips, Addison wrote:
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
Charles McCathieNevile wrote:
On Mon, 15 Dec 2008 22:46:42 +0100, Phillips, Addison addi...@amazon.com
wrote:
Please note that members of the WG also found two minor editorial
issues [3]
[[[
3. Interoperability Considerations: ... such implementations could
return different results from
