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 "Alberto Massari (Resolved) (JIRA)" <xe...@xml.apache.org> on 2012/01/03 18:38:39 UTC
[jira] [Resolved] (XERCESC-1854) Serialization does not detect
invalid XML characters
[ https://issues.apache.org/jira/browse/XERCESC-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alberto Massari resolved XERCESC-1854.
--------------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.0.0)
Assignee: Alberto Massari
A fix is in SVN. Please verify.
> Serialization does not detect invalid XML characters
> ----------------------------------------------------
>
> Key: XERCESC-1854
> URL: https://issues.apache.org/jira/browse/XERCESC-1854
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
> Affects Versions: 3.0.1
> Reporter: Boris Kolpackov
> Assignee: Alberto Massari
> Fix For: 3.2.0
>
> Attachments: test.cxx
>
>
> The attached test case serializes an invalid XML 1.0 document that contains a character with value 0x04. See http://www.w3.org/TR/REC-xml/#NT-Char for the list of valid characters in an XML 1.0 document.
> I've done some digging and it seems that XMLFormatter should check for this. In fast, there is already code for XML 1.1 that checks for these control characters since they need to be escaped in 1.1. It looks like we need to check for invalid characters when in the 1.0 mode. There is the XMLChar1_0::isXMLChar() function which can presumably be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org