Lists Home |
Date Index |
- From: "Rick Jelliffe" <email@example.com>
- To: "Neil Bradley" <firstname.lastname@example.org>, <email@example.com>
- Date: Tue, 5 Aug 1997 23:13:01 +1000
> From: Neil Bradley <firstname.lastname@example.org>
> Reply-to: Peter@ursus.demon.co.uk (Peter Murray-Rust)
> > Therefore I propose that those on XML-DEV who care about this problem come
> > up with some guidelines for implementers.
> I very much hope this happens.
> > This means that the author/processor 'contract' has to be aware of this.
Can I suggest a very different tack?
The problem with CR/LF is one of overloading not of translation or contracts.
They have too many meanings. In particular they function both as
record-start/-end characters and as new-lines.
I suggest that the following approach should be taken. (I think it is the only
realistic solution, especially if we assume that 1) data is usually generated by applications, 2) humans only check and tweak data;
3) we want operating system
and character set independence, 4) line-breaking is generally done by clients
...so CR/LF is basically a convenience for fitting data into editors,
not for the purposes of output.)
**A) XML applications should ignore *ALL* CR and LF as a bad joke. They should
be entirely there for formatting the raw text into nice, eye-sized records.
So CR and LF should never be converted to spaces. (This approach was the
one taken by Interleaf, and I have come to appreciate it.) If you need a
space, then start the new line with it! (Ending the previous line is difficult
**B) XML applications should mandate the use of the unambiguous Unicode characters
-- LINE SEPARATOR
-- PARAGRAPH SEPARATOR
So if I want to do the equivalent of HTML
XML can have:
And it can do this with the text conventions of any operating system.
I certainly think that CR/LF should be not of interest to XML-lang. And I think
they should be of marginal interest to XML applications too. Lets dump them!
xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to email@example.com the following message;
List coordinator, Henry Rzepa (firstname.lastname@example.org)