You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2002/07/12 16:18:03 UTC
DO NOT REPLY [Bug 10727] -
Encoding trouble
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10727>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10727
Encoding trouble
neilg@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From neilg@ca.ibm.com 2002-07-12 14:18 -------
As you're no doubt aware, XML is used in lots of other context than Java; so it
isn't surprising that plugging a Java encoding name into an XML document's
encoding declaration will get you an error--even with a Java parser.
In xerces, we try and encourage document authors to use the IANA aliases for
various encodings, since IANA is a language-independent standard. If you
use "WINDOWS-1250" instead of "Cp1250", your document should validate correctly.
If you really must use the names Java likes to use for encodings, then set the
http://apache.org/xml/features/allow-java-encodings feature to true.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org