This is the mail archive of the mailing list for the GCC 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: contrib/gcc_update in non-english locales

On 22/04/2010 08:59, Paolo Bonzini wrote:
> On 04/22/2010 09:21 AM, Dave Korn wrote:
>> On 22/04/2010 06:17, Basile Starynkevitch wrote:
>>>>> On 04/21/2010 06:25 PM, Basile Starynkevitch wrote:
>>>>>> The contrib/gcc_update script does not seem to work in
>>>>>> non-english locales (e.g. in a French UTF8 locale on Linux).
>> You never told us what the problem actually is
> But I know. :-)  See the links that I posted when I read the reverse patch
> from Basile.
> There are two issues:

  AYS?  I thought the problem was just this:

> revision=`svn info | awk '/Revision:/ { print $2 }'`

> $ svn info /gnu/gcc/gcc
       [ ... ]
> Revision: 158195
       [ ... ]

> $ LANG=fr_FR.UTF-8 svn info /gnu/gcc/gcc
       [ ... ]
> Révision : 158195
       [ ... ]

... i.e. translating the english words causes the match to fail.

> No, C.ASCII is only supported by Cygwin as far as I know.  It works under
> glibc only by virtue of being an unknown locale (so that you end up using
> the default, which is C), but it's not portable.

  Does that mean there's no way to explicitly specify plain ASCII encoding?
Or does it mean you have to use iso-8859-whatever-it-is or one of the codepage
based names?

> C.UTF-8 in particular does not work under glibc (and making it the default
> in Cygwin was a veeeeery bad idea).

  Well, we've had to deal with all the teething troubles, and it seems not to
have been too hard, and I was under the impression we weren't the only
platform to have done this; e.g., from Markus Kuhn's "UTF-8 and Unicode FAQ
for Unix/Linux":
> Red Hat Linux 8.0 (September 2002) was the first distribution to take the
> leap of switching to UTF-8 as the default encoding for most locales. The
> only exceptions were Chinese/Japanese/Korean locales, for which there were
> at the time still too many specialized tools available that did not yet
> support UTF-8. This first mass deployment of UTF-8 under Linux caused most
> remaining issues to be ironed out rather quickly during 2003. SuSE Linux
> then switched its default locales to UTF-8 as well, as of version 9.1 (May
> 2004). It was followed by Ubuntu Linux, the first Debian-derivative that
> switched to UTF-8 as the system-wide default encoding. With the migration
> of the three most popular Linux distributions, UTF-8 related bugs have now
> been fixed in practically all well-maintained Linux tools. Other
> distributions can be expected to follow soon.


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