Encoding "ISO8859_1"?

Archie Cobbs archie at whistle.com
Fri May 12 10:04:39 PDT 2000

Tim Landscheidt writes:
> I'm quite unfamiliar with the Java concept en detail, so
> please forgive my dumbness.
>   (At least) the latest version of Apache JServ
> (1.1.1b2-dev) gives "AJP Protocol Error:
> java.io.UnsupportedEncodingException: ISO8859_1" when run
> under kaffe 1.0.5 but works fine with Sun's JDK 1.2.2. The
> reasons for this error seem to be:
> | src/java/org/apache/jserv/Ajpv12InputStream.java:        return new String(b,"ISO8859_1");
> | src/java/org/apache/jserv/JServConnection.java:            printOut = new PrintWriter(new OutputStreamWriter(this.out,"ISO8859_1"));
> In <URI:http://rufus.w3.org/tools/Kaffe/messages/3548.html>,
> a similar problem is depicted and the necessary patch to
> libraries/javalib/kaffe/io/ConverterAlias.java (that I like
> to propose hereby) is pretty obvious. But I'm curious: Is

OK, "ISO8859_1" should be recognized now..

> there any kind of "IANA" for such Java encodings so one
> could tell whether the name for an encoding is "ISO8859_1",
> "ISO-8859-1", "8859_1", "LATIN1", "IBM819" or "CP819" (and
> therefore, who's to blame if an unknown encoding is used)?
> Or can one just invent them?

Don't know what the official list is. Probably another Sun secret.


Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com

More information about the kaffe mailing list