Re: Compilation Time | More questions -Charsets

["Martin Schlienger" <m.schlienger@xxxxxxxxx>]

Actually since we saw that support for different charsets were
constantly added to GNU/Classpath, this may have been linked with
GNU/Classpath and not jamvm.
Indeed, gnu.java.nio.charset.Provider loads multiple default charsets.
We modify this one as well. It seems that UTF8 , 8859_1 and US_ASCII
are enough to boot. What makes a charset considered mandatory in
GNU/Classpath?

24 Apr 2007 12:05:04 -0600, Tom Tromey <tromey@xxxxxxxxxx>:
> >>>>> "Martin" == Martin Schlienger <m.schlienger@xxxxxxxxx> writes:
>
> Martin> Now we are investigating the charsets classes since for sure we don't
> Martin> need them all on our minimal system. JamVM tries to load a bunch of
> Martin> them when initializing and we would stick to one (8859 or UTF8 for
> Martin> example). You may give us a hint again about how to make jamvm/gnu
> Martin> classpath work with only one charset.
>
> I don't know about jamvm in particular.  In most places, though,
> something like 'file.encoding' chooses the encoding to use.  The
> locale may also affect this.  So as a first attempt I would make sure
> that these things are set properly.
>
> Tom