This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: c/3804: Extended ASCII "wide" characters not behaving with UTF-8 locale
- To: Markus Kuhn <Markus dot Kuhn at cl dot cam dot ac dot uk>
- Subject: Re: c/3804: Extended ASCII "wide" characters not behaving with UTF-8 locale
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Date: Wed, 25 Jul 2001 23:10:02 +0100
- Cc: gcc-bugs at gcc dot gnu dot org
Markus Kuhn wrote:-
> All GNU applications really should be designed such that if you decide
> one morning to follow Plan9 and finally turn everything into UTF-8, then
> all you have to do is add something "export LC_CTYPE=en_GB.UTF-8" to
> /etc/profile, run iconv once over all your plaintext files and filenames,
> and everything works from then on right out of the box in UTF-8 now.
> Everything, except for gcc is seems. Sad. :-(
But what if you're compiling some Japanese software? Do you want
GCC's diagnostics in Japanese? I doubt it.
The way I see it, the locale should determine the diagnostics. The
character sets of input files should be specified independently,
particularly since different files will have different charsets
(e.g. Japanese EUC-jp or Shift-JIS files #including ASCII system
headers).
Neil.