W3C home > Mailing lists > Public > www-xml-blueberry-comments@w3.org > May 2002

RE: need clarification on 2.13 (Normalization Checking)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sun, 26 May 2002 19:13:00 +0200
To: "John Cowan" <jcowan@reutershealth.com>, "Julian Reschke" <julian.reschke@gmx.de>
Cc: <www-xml-blueberry-comments@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCEEJHEKAA.julian.reschke@gmx.de>
> From: John Cowan [mailto:jcowan@reutershealth.com]
> Sent: Sunday, May 26, 2002 7:08 PM
> To: Julian Reschke
> Cc: www-xml-blueberry-comments@w3.org
> Subject: Re: need clarification on 2.13 (Normalization Checking)
>
>
> Julian Reschke scripsit:
>
> > As far as I understand the requirement, any XML 1.0 document that uses
> > Unicode composing characters would become non-wellformed in 1.1, right?
>
> Only if they are used where precomposed characters are already available;
> thus A followed by COMBINING ACUTE is non-WF because A WITH ACUTE
> is available.

OK, this is the case here.

> > If this is the case, protocols that currently use XML 1.0 for
> marshalling
> > will either
> >
> > - have to stay with XML 1.0 or
> >
> > - ensure that composing characters do not appear in protocol messages.
>
> XML is not meant to be a dumping ground for arbitrary sequences of
> Unicode characters without regard to sense.

I didn't mean to say that. It's just that I think that this change will
break more than the editors seem to think, and that those who are affected
are not aware of that. I personally believe that Unicode normalization would
be a good thing.
Received on Sunday, 26 May 2002 13:13:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 29 October 2007 16:58:05 GMT