Re: XML 1.0 serialization [Re: Re: kxml / junit]

Stefan Haustein wrote:

>>so you would do no escaping for \r\n\t for text()? this seems what 
>>Xerces 2 is doing (see below) so i think it is reasonable think to do.
>>
>>however for attributes i think we have to do escaping otherwise all 
>>\r\n\t is normalized to spaces by XML parser. and that is exactly what 
>>Xerces2 is doing (see below) so it looks reasonable for me to do this as 
>>well.
>>    
>>
>
>
>Agreed. I think we should perform no escaping for control codes in text() as one 
>can simply use entityRef("&#xxx;"). For attribute values, let's escape all three 
>codes to avoid distributing attribute values over multiple lines in the 
>serialized output. Also, escaping none/all control codes seems easy to remember 
>and to understand.
>  
>
agreed. please take look on TestSerialize unit tests in cvs and modify 
them if necessary to cover all cases. we should soon have then new 
XmlPull 1.2 stable API release with kXML2, XPP3 and Xerces2 XNI2XmlPull :-)

thanks,

alek

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



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Upgrade to 128-bit SSL Security!
http://us.click.yahoo.com/qZ0LdD/yjVHAA/TtwFAA/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/