This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Almost there...

From: Tom Tromey <tromey at redhat dot com>
To: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
Cc: Norman Hendrich <hendrich at informatik dot uni-hamburg dot de>, java at gcc dot gnu dot org
Date: 22 Jul 2002 21:12:18 -0600
Subject: Re: Almost there...
References: <200207221016.g6MAGb4Z014106@rzdspc1.informatik.uni-hamburg.de><3D3CC58D.7040403@waitaki.otago.ac.nz>
Reply-to: tromey at redhat dot com

>>>>> "Bryce" == Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:

Bryce> Ideally, GCJ should default to the same encoding that javac
Bryce> does on any given system. IIRC the reason why it doesnt is that
Bryce> the system's iconv implementation, used by GCJ, sometimes
Bryce> doesn't support the conversions we need.

There's another issue, too.  On Linux, the `C' locale is very strict
about checking the ASCII encoding.  So by default (assuming no locale
setting) a file with an umlaut is going to give an error with gcj.
However, on the same platform javac will let the file through, since
the JDK appears to use ISO-8859-1 as the default encoding.

The only way I've thought of to fix this is to special case the C
locale.  I think that's pretty ugly, though, so I've resisted the
temptation.  Instead I just reply to the bug reports.

Tom

References:
- Almost there...
  - From: Norman Hendrich
- Re: Almost there...
  - From: Bryce McKinlay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]