You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Vitaly Prapirny (JIRA)" <xe...@xml.apache.org> on 2016/04/07 10:20:25 UTC

[jira] [Commented] (XERCESC-2065) Carriage return entities are not handled properly

    [ https://issues.apache.org/jira/browse/XERCESC-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229890#comment-15229890 ] 

Vitaly Prapirny commented on XERCESC-2065:
------------------------------------------

The CR entity was not removed but printed to the console accordingly. Please redirect the output to a file and see result.

> 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
>
> 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&#13;more&lt;&amp;
> </foo>
> {code}
> Running that through DOMPrint or SAX2Print:
> {code}
> <foo>
> more&lt;&amp;
> </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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org