Altova Mailing List Archives

Re: [xml-dev] XML and mainframes, yet again (was RE: [xml-dev] So mecomments on the 1.1 draft)

From: John Cowan <cowan@-------.----.--->
To: Nicolas LEHUEN <nicolas.lehuen@------.--->
Date: 12/17/2001 10:59:00 AM
Nicolas LEHUEN scripsit:

> Pardon my naive question, but how comes that Unicode, which can handle
> different character representations depending on the encoding used, does not
> have a SINGLE newline codepoint that would map onto 0x0D0A (CRLF) on some
> platform, 0x0D (CR) or 0x0A (LF) on others, 0x85 (NEL) on mainframes, etc. ?

It does: that was why U+2028 LINE SEPARATOR was designed into Unicode.
It was intended to solve the problem once and for all by being Unicode's
only line separator.

In practice, though, people who implemented Unicode retained the platform-
specific line terminator; as a consequence, U+2028 makes the problem

John Cowan               cowan@c...
Please leave your values        |       Check your assumptions.  In fact,
   at the front desk.           |          check your assumptions at the door.
     --sign in Paris hotel      |            --Miles Vorkosigan


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.