"Martin Honnen" <mahotrash@y...> wrote in message 
news:eBoml5sgIHA.944@T......
> Sam Hobbs wrote:
>> "Joe Fawcett" <joefawcett@n...> wrote in message
>
>>> As far as I know not through the XML interfaces. Changing carriage 
>>> returns and new lines to just new line is part of the XML specification 
>>> under the normalizing space rules.
>
>> Do you know what the relevant standard is? I assume it is a RFC.
>
> See <URL:http://www.w3.org/TR/REC-xml/#sec-line-ends>.

That document clearly says "on input" but it is very unclear about output 
(disk) format. If it were to apply to external storage, then it would not be 
possible to have a combination of carriage return and line feed to mark 
End-of-Line in external storage.

It is typical of C/C++ runtime libraries in a Windows environment to convert 
CR and LF to a single LF ('\n') on input but they correspondingly convert a 
single LF to CR and LF.

Files in a Unix/Linux environment usually use a single LF for End-of-Line in 
external storage. This is inconsistent with the definiton of LF. Use of a 
LFCR combination by Windows is consistent with the use of those charcters. 
For email, due to multiple servers and other software (and maybe hardware in 
older systems), it is critical that a standard exist, and that standard is 
CRLF for end-of-line for email.

For HTML and XML, it is probably not critical that there be a standard, but 
if there is, I doubt that it requires that end-of-line for those are just a 
LF.