----- Original Message From: "Frans Englich"
> On Wednesday 03 January 2007 10:00, Henri Sivonen wrote:
>> On Jan 2, 2007, at 17:11, Pete Cordell wrote:
>> > In terms of end-of-line encoding, the approach seems to be to
>> > output what is convenient (CR, LF, or CRLF) and have the receiving
>> > application sort out the situation.
>
> So let me summarize.
>
>...
>
> * End of line characters since the parser normalizes those as well(2.11
> End-of-Line Handling)

On this point I think it might depend what your actual intent is.  If you 
want a byte-for-byte copy after serialization/deserialization, then escaping 
end of line characters is necessary.

However, if you want to convey values that consist of lines of text between 
different platforms, then escaping them may not be appropriate.  For 
example, end-of-lines generated on a Windows system could easily be encoded 
as CRLF.  But it wouldn't be appropriate to force a Unix application to 
consume such an end-of-line convention.  In this case, leaving CR and LF 
unescaped (in element values at least) and leaving the processing to that 
described in section 2.11 mentioned earlier might be more appropriate.

(As much for my own clarification as anything, in the <input 
type='hidden'... example quoted elsewhere needs the first byte-for-byte case 
as the server generating the content eventually becomes the consumer after 
round tripping through the browser.)

Pete.
--
=============================================
Pete Cordell
Tech-Know-Ware Ltd
for XML to C++ data binding visit
http://www.tech-know-ware.com/lmx
(or http://www.xml2cpp.com)
=============================================