|
Quick Lists
|
|
Bug ID:
|
4239372
|
|
Votes
|
1
|
|
Synopsis
|
RFE: Need character converter SPI
|
|
Category
|
java:char_encodings
|
|
Reported Against
|
1.2.1
, kestrel-beta
|
|
Release Fixed
|
|
|
State
|
11-Closed, duplicate of 4287465,
request for enhancement
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4284917
,
4287465
|
|
Submit Date
|
18-MAY-1999
|
|
Description
|
The classes sun.io.{ByteToChar CharToByte}Converter provide a mechanism for adding character encodings.
There is no other simple way of doing this. Keep the
implementations of the standard character encodings part of
the implementation, but there should be a way to extend the
character encodings by creating and registering an implementation
of the new encodings with a standard class.
(Review ID: 83223)
======================================================================
|
|
Work Around
|
Reimplement the character encoding lookup and registrations
in user code, wrap the builtin character encodings, and avoid
all of the methods that take a builtin character encoding
string.
======================================================================
|
|
Evaluation
|
Will be addressed under RFE 4287465.
xxxxx@xxxxx 2000-01-26
|
|
Comments
|
Submitted On 20-AUG-1999
DaleKing
Please add this capability. I have cases where
the encoding is unique for a given application and
doesn't agree with any of the standard encodings.
Submitted On 20-AUG-1999
johnl@vizdom.com
Fwiw, Bug 4228207 is a related but different
request. There the builtin encoding classes
are more exposed. Here, it is possible to define
new encoders.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |