This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: UnsupportedEncodingException
Michael Koch wrote:
> On Wednesday 29 September 2004 09:13, Mohan Embar wrote:
>
>>Hi Melanie,
>>
>>
>>>How can i used other encodings? especially
>>>windows-1256 or Cp1256? I tried code using
>>>'windows-1256' under linux and and it worked correctly
>>>without any class references.
>>
>>This probably has to do with the fact that the MinGW
>>build doesn't use libiconv and the Linux builds do.
>>The encoding you mentioned isn't one of the standard
>>gcj encodings. I'm not knowledgeable enough about this
>>to elaborate further.
>
>
> "UTF-8" is a standard encoding, "windows-1256" is obviously not.
> (According to
> http://java.sun.com/j2se/1.4.2/docs/api/java/nio/charset/Charset.html)
>
> I'm pretty sure the 6 charsets mentioned there are standard of whole
> JDK, not only java.nio.charset.
>
Sun's specification only mandates the 6 charsets, but their implementation
supplies many more.
There doesn't seems to be any reason that libgcj could not supply extra
Charsets if desired. I don't think the goal should be to do the minimum
necessary to meet the spec.
The patch I posted in this message:
http://gcc.gnu.org/ml/java/2004-09/msg00174.html
might be useful. One problem I see with the current Charset implementation
is that all possible charsets are initialized when the Charset class is
initialized. It might be a good idea to only initialize them on demand.
David Daney.