This is the mail archive of the
mailing list for the GCC project.
Re: gcc compile-time (multibyte issue)
- From: Tom Tromey <tromey at redhat dot com>
- To: dewar at gnat dot com (Robert Dewar)
- Cc: jsm28 at cam dot ac dot uk, gcc at gcc dot gnu dot org, zack at codesourcery dot com
- Date: 31 May 2002 13:04:16 -0600
- Subject: Re: gcc compile-time (multibyte issue)
- References: <20020519183512.7B980F28CC@nile.gnat.com>
- Reply-to: tromey at redhat dot com
>>>>> "Robert" == Robert Dewar <email@example.com> writes:
Robert> What encodings does Java implement. I am not sure what using
Robert> the locale means in all cases.
gcj uses the encodings provided by the host's iconv().
It also implements its own UTF-8 reader as a fallback.
In practice this means that on Linux we support every encoding, and on
other platforms we support only UTF-8. (There may be some exceptions,
but that is the general rule.)
"Using the locale" means that, on systems that support it, we use
nl_langinfo(CODESET) to determine the default encoding. The
--encoding command-line option can be used to override this.
We do this because this is what JDK users expect.