[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ 100190 ] EncodingManager mapping for ISO-8859-1
From: |
nobody |
Subject: |
[ 100190 ] EncodingManager mapping for ISO-8859-1 |
Date: |
Fri, 16 Nov 2001 11:15:46 -0500 |
Support Request #100190, was updated on 2001-Nov-13 16:22
You can respond by visiting:
http://savannah.gnu.org/support/?func=detailsupport&support_id=100190&group_id=85
Category: java.io
Status: Open
Priority: 5
Summary: EncodingManager mapping for ISO-8859-1
By: mark
Date: 2001-Nov-16 17:15
Message:
Logged In: YES
user_id=301
Browser: Mozilla/5.0 Galeon/0.12.7 (Linux i586; U;) Gecko/20011023
See also the workaround in the following message:
<http://mail.gnu.org/pipermail/classpath/2001-November/001630.html>
----------------------------------------------------------------------
By: cbj
Date: 2001-Nov-13 16:22
Message:
Logged In: YES
user_id=303
Browser: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4)
Gecko/20010913
Properties.load opens an InputStreamReader with
decoder "ISO-8859-1".
In java.io.EncodingManager the decoder is mapped to the
class gnu.java.io.DecoderISO-8859-1, which doesn't exists.
The close and obvious match is gnu.java.io.Decoder8859_1
Fix:
----
"ISO-8859-1" is the string used in the (Java)
documentation.
I think the Encoder and Decoder classes should be renamed
from Encoder8859_1 to EncoderISO-8859-1 and so on.
How did it happen:
------------------
I executed SpecApplication from the SpecJVM benchmark suite
on my Jaos VM.
Submitted originally by Patrik Reali, address@hidden
----------------------------------------------------------------------
You can respond by visiting:
http://savannah.gnu.org/support/?func=detailsupport&support_id=100190&group_id=85