[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <adaljgqz0ff.fsf@roland-alpha.cisco.com>
Date: Fri, 25 Dec 2009 22:58:28 -0800
From: Roland Dreier <rdreier@...co.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Sergei Trofimovich <slyich@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Michal Marek <mmarek@...e.cz>,
Sergei Trofimovich <slyfox@...ox.ru>
Subject: Re: [PATCH] Kbuild: set LC_MESSAGES=C (as LC_CTYPE=C is)
> > Seems unfortunate to lose localized error messages. (Although in my
> > en_US.UTF-8 case, all I get is non-ASCII quote characters)
> The whole problem is that for some people we lose *all* messages. This
> seems all very strange to me at all, but I guess it tweaks some internal
> detail inside the glibc message library, sigh.
I just meant that people used to be able to get localized error messages
by setting LANG or whatever. And now they're stuck with ASCII english.
> > This all started because of the awk invocation in arch/x86/lib. Maybe
> > the best idea would be to confine the locale monkeying to that one
> > place?
> Except that sed, etc. and even the shell itself have the same class of
> problems. Perl doesn't, since it has saner rules for how regular
> expressions handle ranges.
But pretty much everyone on a modern distro has had a UTF8 locale for
quite a while. And as far as I know there have been no problems caused
by collation order or anything else. So this change to always build in
the C locale is just worrying about theoretical problems.
Anyway, not a big deal I guess.
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists