[
https://issues.apache.org/jira/browse/XERCESC-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263333#comment-15263333
]
Scott Cantor edited comment on XERCESC-2065 at 4/29/16 12:41 AM:
-----------------------------------------------------------------
The proposed patch changes the "character encoding" mode of the XMLFormatter to
include carriage returns as a character to encode.
The test file correctly prints with DOMPrint, etc.
{code}It does use 
 and not but that should be equivalent once
parsed.{code}
was (Author: [email protected]):
The proposed patch changes the "character encoding" mode of the XMLFormatter to
include carriage returns as a character to encode.
The test file correctly prints with DOMPrint, etc. It does use 
 and not
but that should be equivalent once parsed.
> Carriage return entities are not handled properly
> -------------------------------------------------
>
> Key: XERCESC-2065
> URL: https://issues.apache.org/jira/browse/XERCESC-2065
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM, Non-Validating Parser, SAX/SAX2
> Affects Versions: 3.1.3
> Reporter: Scott Cantor
> Priority: Critical
> Attachments: xercesc-2065.patch
>
>
> Documents with CR entities don't seem to round trip properly in the parser if
> you parse them and then serialize them. It's possible the bug is in the
> serializer because signed documents don't end up with corrupt signatures, but
> that may be due to insufficient testing as of yet.
> A simple example:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <foo>
> text more<&
> </foo>
> {code}
> Running that through DOMPrint or SAX2Print:
> {code}
> <foo>
> more<&
> </foo>
> {code}
> Notice the CR entity is removed, but also all of the characters immediately
> in front of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
