Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] How to handle "newline" characters in an XML parser.

From: richard@---.--.--.-- (------- -----)
To: xml-dev@-----.---.---
Date: 12/5/2006 7:38:00 PM
In article <e24752a10612051124j501ffe3i7469c64a94ea4959@m...> you write:

>I'm having some trouble figuring out how to handle "newline"
>characters in XML text files on different platforms. I typically
>ignore all whitespace in the parser,

To conform to the standard, an XML parser must return all whitespace
in content to the application, except that line breaks must be
normalized to a linefeed character.  The idea is that XML applications
don't have to worry about the platform's line-end conventions.  Any of
the following count as a line break: LF, CR LF, and CR not followed by
LF.  So if you get two CRs followed by a LF, you should return two
LFs.  The easiest way to do this is to convert them as you input them,
before parsing.  You can count line numbers at the same time.

-- Richard


transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent