KB Article #69291
In Integrator XML Parser records \n as a character when it shouldn't
In Integrator with XML parser, if you set a field of fixed length m and input a string of m charachters and a \n, it will throw an error:
procengine(procengine(hierchmsgenv)):[CNV - 9002]: Field too long (13), defined length is m
Resolution
* Refer link: http://www.w3.org/TR/2006/REC-xml11-20060816/#sec-line-ends
2.11 End-of-Line Handling
XML parsed entities are often stored in computer files which, for editing convenience, are organized into lines. These lines are typically separated by some combination of the characters CARRIAGE RETURN (#xD) and LINE FEED (#xA).
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 all of the following to a single #xA character:
the two-character sequence #xD #xA
the two-character sequence #xD #x85
the single character #x85
the single character #x2028
any #xD character that is not immediately followed by #xA or #x85.
The characters #x85 and #x2028 cannot be reliably recognized and translated until an entity's encoding declaration (if present) has been read. Therefore, it is a fatal error to use them within the XML declaration or text declaration.
So the XML standard states that the \n character is not ignored, unlike the CR (0x0D or \r).