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: Anne van Kesteren <annevk@opera.com>
Date: Fri, 30 Jan 2009 16:01:53 +0100
To: "Richard Ishida" <ishida@w3.org>, public-i18n-core@w3.org, www-style@w3.org
Message-ID: <op.uokr1fv564w2qv@annevk-t60.oslo.opera.com>

On Fri, 30 Jan 2009 15:54:45 +0100, Richard Ishida <ishida@w3.org> wrote:
>> 1) Do browsers normalize currently?
> The emails below point to some tests and results that show that the  
> major browsers on XP currently don't normalise class names and selectors  
> before comparing.

Ok, that's what I expected.

>> 2) Assuming they do not, who have complained?
> I don't think we can build the Web purely on the basis of what people  
> have complained about in the past.  The Web needs to be built in the  
> most accessible way possible, and we need to, where we can, anticipate  
> future issues.  In this case, these issues are likely to touch most on  
> developing parts of the world who probably haven't yet found their voice  
> to a large extent.  But I suspect they will, and I think we have a  
> responsibility to bear them in mind so that the Web can be used more  
> universally, at the same feature and usability levels.  Consider the  
> hoops we are asking them to jump through as alluded to in the mail  
> pointed to below.  Wouldn't you complain?

It seems that having authoring tools that just output e.g. NFC would do  
the trick for those users. Letting Unicode Normalization affect IDs, class  
names, and HTML parsing does not seem like a good idea at all. Especially  
not retroactively as that could mean that duplicate IDs arise documents  
that do not have them per todays rules. As far as I can tell XML does not  
do this either.

Anne van Kesteren
Received on Friday, 30 January 2009 15:02:35 UTC

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