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

Re: [CSS21][css3-namespace][css3-page][css3-selectors][css3-content] Unicode Normalization

From: Henri Sivonen <hsivonen@iki.fi>
Date: Fri, 6 Feb 2009 13:06:39 +0200
Cc: public-i18n-core@w3.org, "'W3C Style List'" <www-style@w3.org>
Message-Id: <172B0A37-3FE3-427E-96B9-9A66EB57D133@iki.fi>
To: David Clarke <w3@dragonthoughts.co.uk>

On Feb 6, 2009, at 12:34, David Clarke wrote:

> In an ideal world, fixing all the IME systems to produce normalised  
> results would be great, but highly impractical.

It's also highly impractical to change comparisons for symbols (that  
have a textual interpretation) all over. They are in a lot of places  
beyond browsers. Where would you draw the line? If you got Selectors  
to normalize, you you ask JavaScript to change next? If you got  
JavaScript to normalize function names for dispatch, would you ask  
Java to change? Would a dynamic library linker on an embedded system  
with no text-related UI have to perform normalization upon loading  

> Decisions would also need to be made regarding which normalized from  
> is the "correct one", and those decisions would need to be complied  
> with.

NFC, of course. :-)

Henri Sivonen
Received on Friday, 6 February 2009 11:07:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:04 UTC