W3C home > Mailing lists > Public > www-style@w3.org > February 2009

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

From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Date: Tue, 10 Feb 2009 22:35:53 +0100
Message-ID: <4991F339.3070707@disruptive-innovations.com>
To: "Phillips, Addison" <addison@amazon.com>
Cc: Thomas Phinney <thomas.phinney@gmail.com>, Mark Davis <mark.davis@icu-project.org>, Richard Ishida <ishida@w3.org>, Anne van Kesteren <annevk@opera.com>, Henri Sivonen <hsivonen@iki.fi>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, "www-style@w3.org" <www-style@w3.org>, Peter Edberg <pedberg@apple.com>, Deborah Goldsmith <goldsmit@apple.com>

Phillips, Addison wrote:
> I think Daniel was trying to illustrate the character sequence rather than saying that there is a bug in the renderer. On a Mac, he sees an e-accute. It is encoded as <0065 0301> rather than as <00E9>, at least in the filesystem. Either is acceptable in a Unicode text file: they are canonically equivalent, after all.
> The W3C has long recommended (or at least tried to recommend via CharMod-Norm) the use of NFC for interchange on the Web. Even absent any changes to Selectors, that recommendation is unlikely to go away. What we're discussing is whether specifications sensitive to normalization should deal with the fact that many systems (Macs are not alone in this) do not use NFC at all times or for all languages. 
> Addison

Absolutely. Thanks for normalizing my prose into something readable ;-)

Received on Tuesday, 10 February 2009 21:36:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:24 UTC