• To: xml-dev@l...
• Subject: Re: carriage return handling in XML parsers
• From: Richard Tobin <richard@c...>
• Date: Thu, 11 Apr 2002 14:19:03 +0100 (BST)
• Cc:
• In-reply-to: <LOBBICBLDJIJHPNJFPOLMEMICDAA.mike@a...>
• Organization: HCRC, University of Edinburgh

>It would appear that given this section, it is never possible 
>to get unaccompanied carriage return "characters" in the 
>stream of information provided by an XML parser, be it
>SAX or DOM, unless I encode these as character references
>in the input file to the parser. Is this correct?

Yes.

>On a related note, assuming simple ascii files, if I now 
>encode the carriage return as a character reference, and 
>round trip the file through an XSLT identity transform, 
>will the output file be identical or will the carriage 
>return now be represented as a single <CR> byte?

Ooh, good question.  It seems to me that XSLT ought to re-escape it,
since it's supposed to output an XML file that would produce the same
thing when read in again.  But the two XSLT processors that I have
to hand (xt and saxon, both probably rather old) just output CR
characters.

-- Richard

• References:
  • carriage return handling in XML parsers
    • From: "Michael Leditschke" <mike@a...>

• Prev by Date: RE: MS to shelve Hailstorm / .NET My Services?
• Next by Date: RE: A Query about View Construction in XML
• Previous by thread: carriage return handling in XML parsers
• Next by thread: RE: carriage return handling in XML parsers
• Index(es):
  • Date
  • Thread