Bug ID: JDK-6895737 Big5-HKSCS encodings change in behavior b/w Java1.4.2 and Java 5.0/6

Type: Bug
Component: core-libs
Sub-Component: java.nio.charsets
Affected Version: 5.0u16

Priority: P2
Status: Closed
Resolution: Not an Issue
OS: solaris_10
CPU: x86

Submitted: 2009-10-27
Updated: 2011-02-16
Resolved: 2010-02-10

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

Other
5.0-poolResolved

The test case for Solaris attached to this bug report.

The attachment JSData.zip contains :
1. input.txt - input to test case
2. output.txt (2 files) showing o/p for 142 and 150
3. TestCase itself  (Converter.java)

output.txt content is different if the test case is executed with Java 5.0 or Java 6 vs. Java 1.4.2.

EVALUATION As mentioned, its not a BUG, I am closing this bug too.
10-02-2010
EVALUATION The licensee has finally agreed to close this issue and agrees with the evaluatinon. I am not closing out the bug as the previous comment notes fixing another bug (4426415) to avoid confusion. I will leave it to Vaibhav to determine how to proceed. The licensee is not interested in tracking it further.
10-12-2009
EVALUATION We should consider fixing 4426415 to avoid confusions and incompatibility problems coming from encoding revisions.
05-11-2009
EVALUATION jdk5.0/6 and later use HKSCS_2001. jdk1.4.2 uses "old" version of HKSCS. They have different mappings for "some" characters, 0xfa42, the problematic character in this case is one of them. This is NOT a bug.
04-11-2009

Relates :	JDK-4750497 - HKSCS-2001 support
Relates :	JDK-4426415 - (cs) Charset naming scheme is insufficient