Name: gm110360 Date: 10/21/2002


FULL PRODUCT VERSION :
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)

FULL OPERATING SYSTEM VERSION : windows 2000


A DESCRIPTION OF THE PROBLEM :
Character endodings of "JIS201", "JIS208", "JIS212" worked
fine in 1.3.1. Now they fail in 1.4.x, and we notice that
these encodings are no longer listed in the list of
supported encodings, and our application is completely broken.

Oddly however, when we try to use these encodings we are not
getting an UnsupportedEncodingException, they just aren't
working properly.

We are doing this because we need to support the peculiar
encoding of various international character sets in DICOM
which uses ISO 2022 escapes in a fairly general fashion.

In order to achieve this, having extracted the subcomponents
of byte arrays between escape sequences that use a specific
encoding (like JIS 201 or 208 or 212), then we use the
encodings supplied and previously supported by the names of
"JIS201", "JIS208", "JIS212" to do the hard work using "new
String(bytes, offset, length, useEncoding);".


REGRESSION. Last worked in version 1.3.1

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER WORKAROUND :
Haven't been able to find one despite trying all the other
relevant supported encodings listed.

Release Regression From : 1.4.0_02
The above release value was the last known release where this
bug was known to work. Since then there has been a regression.

(Review ID: 165702)
======================================================================