W3C home > Mailing lists > Public > xml-editor@w3.org > July to September 2000

clause 2.11

From: Karlsson Kent - keka <keka@im.se>
Date: Mon, 11 Sep 2000 15:52:23 +0200
Message-ID: <C110A2268F8DD111AA1A00805F85E58DA68921@ntgbg1>
To: 'xml-editor@w3.org' <xml-editor@w3.org>


Clause 2.11 now says:

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).

[E86]To simplify the tasks of applications , an XML processor must normalize
line breaks in parsed entities to #xA either by translating the
two-character sequence #xD #xA and any #xD that is not followed by #xA to
#xA on input before parsing, or by using some other method such that the
characters passed to the application are the same as if it did this
translation.

===================
This does not cover all NLFs (see UTR No. 13).

Suggested changed text:
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), but may also be separated by vertical-tabulation (#xB), form-feed
(#xC), next-line (#x85), line separator (#x2028), or paragraph separator
(#x2029).

To simplify the tasks of applications, an XML processor must normalize line
breaks in parsed entities to #xA either by translating the two-character
sequence #xD #xA, any #xD that is not followed by #xA, any #x85, any #2028,
and any #2029 to #xA on input before parsing, or by using some other method
such that the characters passed to the application are the same as if it did
this translation.  For compatibility, only #xD, #xA, and #xD #xA should be
used for line separation.

		/Kent Karlsson
Received on Monday, 11 September 2000 09:54:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:31 GMT