[ http://issues.apache.org/jira/browse/XERCESJ-1049?page=comments#action_61682 ] Michael Glavassevich commented on XERCESJ-1049: -----------------------------------------------
The IANA side of the EncodingMap only contains encoding names and aliases registered with IANA [1]. There's a feature [2] when enabled that will cause the parser to recognize Java encoding names. It may be that the Java encoding side of the map is missing the reverse mapping. [1] http://www.iana.org/assignments/character-sets [2] http://xml.apache.org/xerces2-j/features.html#allow-java-encodings > org.apache.xerces.util.EncodingMap should recognise Java-style encodings > ------------------------------------------------------------------------ > > Key: XERCESJ-1049 > URL: http://issues.apache.org/jira/browse/XERCESJ-1049 > Project: Xerces2-J > Type: Bug > Versions: 2.6.2 > Environment: all > Reporter: J�rg Henne > > Xerces 1 supported encodings of the kind "Cp1141" etc. Xerces 2 fails to > parse InputSources with this (and other) encodings, because the 4-digit code > page ("CpXXXX") encodings have IANA-side entries for "CP0XXXX" only. > For backwards compatibility, Xerces 2 should support the encodings without > the leading 5th digit, too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
