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: Tue, 3 Feb 2009 10:43:30 +0200
To: Andrew Cunningham <andrewc@vicnet.net.au>
Message-Id: <47002D57-020A-4974-8D1B-5360A448F7C0@iki.fi>
Cc: "Boris Zbarsky" <bzbarsky@MIT.EDU>, public-i18n-core@w3.org, "W3C Style List" <www-style@w3.org>

On Feb 2, 2009, at 17:18, 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.
> Normalisation in some context may violate standards in some  
> industries.
> One taht comes to mind is libraries. Many of the newer integrated  
> library
> management systems will use a web browser as a client for the  
> cataloguing
> modules. Normalising form fields would result in violating the MARC21
> character model.
>
> If i were working on content in some langauges like igbo, and wanted  
> to
> include tone markers to use as an alternative display of data, its  
> easier
> to work with NFD data and filter tone marks out when applying standard
> orthographic views.

Surely a MARC21-based system should then use this data representation  
internally but not leak it to a Web UI for the system.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Tuesday, 3 February 2009 08:44:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 February 2009 08:44:12 GMT