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: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 02 Feb 2009 10:27:56 -0500
Message-ID: <498710FC.5040101@mit.edu>
To: Andrew Cunningham <andrewc@vicnet.net.au>
CC: public-i18n-core@w3.org, W3C Style List <www-style@w3.org>

Andrew Cunningham wrote:
> On Tue, February 3, 2009 1:42 am, Boris Zbarsky wrote:
>> Andrew, forgive my ignorance, but does this mean that normalizing
>> everything in the UA at parse-time (and normalizing the content of form
>> fields that the user types in at typing time, of course) is not in fact
>> a viable option?
> the normalisation of form fields should be determined the web developer.

The normalization of the fields themselves, or the normalization of the 
submitted data?

Admittedly, the line is blurry if you "submit" the data by reading it 
from the DOM and sending it with XMLHttpRequest.  But any data in the 
DOM or CSSOM can be sent that way, implying that nothing may ever be 
normalized in storage, correct?  In other words, all normalization would 
have to be performed at compare time and only at compare time?

> selectors should be consistently normalised, and NFC would be appropriate.
> Search strings are also a good example of where normalisation is
> important.

Indeed, this was an important use case I was considering when I asked my 
form controls question.

> certain things require normalisation, certain things should be at the
> discretion of the developer.

It's not clear to me how the UA can figure out which is which, honestly.

-Boris
Received on Monday, 2 February 2009 15:28:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 February 2009 15:28:44 GMT