DOMWriterImpl (which got renamed to DOMSerializerImpl back in Xerces
2.5.0) hasn't existed for a long time so I'd venture to guess that the
code which checks whether a character needs to be written as a character
reference for a specific encoding wasn't mature yet. Was probably doing
something naive like:
if (ch <= 0x7f) {
writeChar(ch);
}
else {
writeCharRef(ch);
}
As Joe already pointed out, if your application cares about this
difference you should fix it.
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]
R Subram <[EMAIL PROTECTED]> wrote on 08/10/2007 01:46:54 PM:
> Thanks for your response.
>
> I'm not being rude here. Why did it work when I was using
> DOMWriterImpl and not in LSSerializer?
>
>
> Subject: Re: Equivalent of DOMWriterImpl in Xerces2.7
> To: j-users@xerces.apache.org
> From: [EMAIL PROTECTED]
> Date: Fri, 10 Aug 2007 13:28:15 -0400
>
> As far as XML is concerned, there is absolutely no semantic
> difference between a character and its Numeric Character Reference
> form. XML parsers generally discard this distinction; XML
> serializers generally write out the character unless the encoding
> can't represent it (forcing the numeric form).
>
> If your application cares about this difference, fix your app.
>
> ______________________________________
> "... Three things see no end: A loop with exit code done wrong,
> A semaphore untested, And the change that comes along. ..."
> -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.
> org/pegasus/songs/threes-rev-11.html)
>
> Recharge--play some free games. Win cool prizes too! Play It!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
