Re: [xml-dev] XML 1.1 requires entity resolution, XInclude processing, and more

At 3:39 AM +1000 4/30/02, Rick Jelliffe wrote:

>So I don't think that simple normalization and simple normalization-
>checking is difficult or will cause performance penalties for
>most Western and Chinese data. The performance penalty will be
>borne by the documents that actually require the checks.
>

That may be true on parsing. I'm more concerned about generating text 
though, specifically typing it in an editor of some kind. If the 
editor chooses to represent e acute as e+combining accent acute, it 
may be difficult for the user to pick a different representation. 
Even if the editor allows the distinction to be made, it may not be 
at all obvious to the author why the parser is complaining about an 
apparently legal character. We already see plenty of problems with 
new users who don't understand why their accented characters cause 
malformedness errors. This seems likely to increase the problem. 
Correctly labeled, Unicode-legal documents can now be malformed 
because of character representation issues.
-- 

+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold |  | Writer/Programmer |
+-----------------------+------------------------+-------------------+
|          The XML Bible, 2nd Edition (Hungry Minds, 2001)           |
|             http://www.cafeconleche.org/books/bible2/              |
|   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
+----------------------------------+---------------------------------+
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
|  Read Cafe con Leche for XML News: http://www.cafeconleche.org/    |
+----------------------------------+---------------------------------+