- From: Anne van Kesteren <annevk@opera.com>
- Date: Wed, 04 Feb 2009 18:01:40 +0100
- To: "Robert J Burns" <rob@robburns.com>, "Aryeh Gregor" <Simetrical+w3c@gmail.com>
- Cc: public-i18n-core@w3.org, jonathan@jfkew.plus.com, "W3C Style List" <www-style@w3.org>
On Tue, 03 Feb 2009 19:38:32 +0100, Robert J Burns <rob@robburns.com> wrote: > Anne wrote: >> (As far as I can tell XML is Unicode >> Normalization agnostic. It merely recommends authors to do a certain >> thing. We can certainly recommend authors to do a certain thing in HTML >> and CSS too...) > > XML is not Unicode agnostic. I did not say that. > Unicode is a normative reference in terms of text handling. So an XML UA > is by definition also a Unicode UA. That means that an implementation > needs to have some reason for comparing two byte-wise unequal though > canonically equivalent strings and determining they do not match. I > haven't heard anyone here say why an XML processor needs to support (and > therefore promote) such errors. The XML grammar is expressed in Unicode codepoints so comparison also happens on that level. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Wednesday, 4 February 2009 17:02:26 UTC