Hi,
There is no rule here as far as I know. We just register all the
charsets we have. Adding a charset is done either because it is
specified by the standard, or because someone needed it.
I know I should have answered earlier. The standard charsets are chosen
according to Sun's
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
Martin == Martin Schlienger [EMAIL PROTECTED] writes:
Martin Actually since we saw that support for different charsets were
Martin constantly added to GNU/Classpath, this may have been linked with
Martin GNU/Classpath and not jamvm.
Martin Indeed, gnu.java.nio.charset.Provider loads multiple
ok, thanks for that, I may move to Eclipse if needed.
Actually we are hacking the ClassLoader in a way we break Java Spec,
so this may not be really interested for main maintainers. The idea is
to split the glibj.zip: the very useful class to boot the VM (jamvm)
and our custom ClassLoader are
Martin == Martin Schlienger [EMAIL PROTECTED] 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).
5 matches
Mail list logo
