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 2001/02/26 19:43:52 UTC
[Bug 715] New - encoding 8859_1 rejected even with allow-java-encodings
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=715
*** shadow/715 Mon Feb 26 10:43:52 2001
--- shadow/715.tmp.18889 Mon Feb 26 10:43:52 2001
***************
*** 0 ****
--- 1,24 ----
+ +============================================================================+
+ | encoding 8859_1 rejected even with allow-java-encodings |
+ +----------------------------------------------------------------------------+
+ | Bug #: 715 Product: Xerces-J |
+ | Status: NEW Version: 1.3.0 |
+ | Resolution: Platform: PC |
+ | Severity: Normal OS/Version: |
+ | Priority: Component: Core |
+ +----------------------------------------------------------------------------+
+ | Assigned To: xerces-j-dev@xml.apache.org |
+ | Reported By: nboyd@atg.com |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ We've been using the "http://apache.org/xml/features/allow-java-encodings"
+ feature in order to handle Java encodings used in the J2EE conformance test
+ suite. Unfortunately, Xerces still gives an error for an invalid encoding for
+ the Java encoding name "8859_1" since it doesn't begin with [A-Z][a-z].
+
+ I'll attach a patch that addresses this problem. The change is simple: the
+ value of the feature flag is passed down to the method that performs the
+ check, allowing it to accept the Java encoding name.