Kbase P45384: The XML parser replaces Carriage Returns (CHR 13) with Line Feeds (CHR 10)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/14/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
SYMPTOM(s):
The XML parser replaces Carriage Returns (CHR 13) with Line Feeds (CHR 10)
Carriage Returns are being interpreted as Line Feeds
XML documents lose the Carriage Return character
CAUSE:
This behavior expected behavior for an XML parser. The XML Specification at http://www.w3.org/TR/REC-xml/#sec-line-ends mentions the following:
Section 2.11 End-of-line handling
To simplify the tasks of applications, the XML processor MUST behave as if it normalized all line breaks in external parsed entities (including the document entity) on input, before parsing, by translating both the two-character sequence #xD #xA and any #xD that is not followed by #xA to a single #xA character.
FIX:
Choose a Valid delimiter as specified in the XML specification.