[
https://issues.apache.org/jira/browse/XERCESC-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1336.
------------------------------------
Resolution: Won't Fix
Doesn't seem there is anything we can do. Workaround is available.
> Xerces C++ defines an encoding-string that Xerces/Java refuses to parse
> -----------------------------------------------------------------------
>
> Key: XERCESC-1336
> URL: https://issues.apache.org/jira/browse/XERCESC-1336
> Project: Xerces-C++
> Issue Type: Bug
> Affects Versions: 2.6.0
> Environment: Solaris 6, XercesJ 2.4
> Reporter: Dominik Stadler
> Priority: Minor
>
> We are using Xerces C++ to create XML-Messages that are later parsed by
> Xerces/Java.
> When we use the define XMLUni::fgISO88591EncodingString for setting the
> encoding, the XML-Message contains "ISO8859-1", because the string is defined
> as
> "chLatin_I, chLatin_S, chLatin_O, chDigit_8, chDigit_8, chDigit_5, chDigit_9,
> chDash, chDigit_1, chNull".
> When we later use Xerces/Java to parse this file, we get the following error:
> [Fatal Error] :1:43: Invalid encoding name "ISO8859-1".
> It seems that Xerces/Java only knows the encoding "ISO-8859-1" (with a dash),
> but not "ISO8859-1" (without dash).
> The XML-Specification states that "ISO-8859-1" (with a dash) SHOULD be used,
> look at http://www.w3.org/TR/2004/REC-xml-20040204/#charencoding
> Additionally the file src/xercesc/util/XMLUni.cpp defines more variants of
> the encoding, where we are not sure which of them are supported by
> Xerces/Java.
> So in my opinion either Xerces C++ should not provide that define any more,
> or Xerces/Java should be enhanced to accept that encoding-string.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
