Re: Re: kxml / junit

Stefan Haustein wrote:

>>i think serializer only need to escape \r, pass through \n and \t and 
>>otherwise throw error if ch <32.
>>    
>>
>
>Alek,
>
>I am not sure whether this is really a good idea: How would one write XML files 
>respecting the line-end encoding of the current platform? I think a better 
>approach would be to write anything < " " legal in 1.1 to the stream without 
>escaping and refer to entityRef("&#13;") in the text()-documentation.
>  
>
i think baseline shoul dbe XML 1.0?

in XML 1.0

\r -> &#13; (to respect EOL as otherwise it may get normalized!)
\n, \t -> without chnage
<32 illegal

this will make it totally consistent with XML 1.0 and minimize =chanvces 
of situation that you use XmlSerializer to write output that can not be 
parsed by XML 1.0 parser!

i think XML 1.1 is really of very low priority  - what is number of XML 
1.1 documents compared to 1.0?

what do you think?

thanks,

alek

-- 
The best way to predict the future is to invent it - Alan Kay



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/2U_rlB/TM
---------------------------------------------------------------------~->

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/xmlpull-dev/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/