Lists Home |
Date Index |
- To: firstname.lastname@example.org
- Subject: question w.r.t.: Extensible Markup Language (XML) 1.0 (Third Edition)
- From: Harrie Hazewinkel <email@example.com>
- Date: Fri, 17 Sep 2004 11:29:20 +0200
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030
I have a question with respect to the Extensible Markup Language (XML)
1.0 (Third Edition) standard of "http://www.w3.org/TR/REC-xml".
In this section it specifies the handling of CRLF.
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 both the
two-character sequence #xD #xA and any #xD that is not followed by #xA
to a single #xA character.
But how about this piece of XML (part of SyncML),
Hazewinkel\r\nAttendees: \r\nHarrie Hazewinkel +\r\nAntonio Amadori^M
?\r\nGastone Amadori ?\r\n~~~~~~~~~~~~~~~~~~~~\r\nI like to keep^M
inviting you. :-)\r\n^M
The data is here between the <Data> and </Data> tags.
This is a calendar element which by mime type must keep
the CRLF after each line. This is made visible with the '^M'<linefeed>
Would the lines describing the event also fall
under the section described above? If so XMl changes data and one
cannot get back it, I guess.
Would this not a problem with the current specification?