From: "H. Peter Anvin" <hpa@zytor.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Sergei Trofimovich <slyich@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Michal Marek <mmarek@suse.cz>,
Sergei Trofimovich <slyfox@inbox.ru>
Subject: Re: [PATCH] Kbuild: set LC_MESSAGES=C (as LC_CTYPE=C is)
Date: Sat, 26 Dec 2009 12:04:57 -0800 [thread overview]
Message-ID: <4B366C69.9010700@zytor.com> (raw)
In-Reply-To: <adar5qizg6w.fsf@roland-alpha.cisco.com>
On 12/25/2009 05:17 PM, Roland Dreier wrote:
>
> > The whole reason with only setting some LC_* to C was to be able to
> > leave LC_MESSAGES intact, but it seems it breaks on too many real-life
> > systems.
>
> > As such, I suggest we should set LC_ALL=C and get rid of the rest of it:
>
> Seems unfortunate to lose localized error messages. (Although in my
> en_US.UTF-8 case, all I get is non-ASCII quote characters)
>
> 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?
>
It is also possible that setting only LC_COLLATE will solve the most
fundamental problem, which is the one of character ranges. LC_COLLATE
probably will interfere less with LC_MESSAGES than the setting of LC_CTYPE.
It's still bloody broken that glibc malfunctions like that for an
LC_MESSAGES/LC_CTYPE intentional mismatch, but, sigh, that's glibc for you.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-12-26 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 17:13 [PATCH] Kbuild: set LC_MESSAGES=C (as LC_CTYPE=C is) Sergei Trofimovich
2009-12-25 23:36 ` H. Peter Anvin
2009-12-26 1:17 ` Roland Dreier
2009-12-26 1:30 ` H. Peter Anvin
2009-12-26 6:58 ` Roland Dreier
2009-12-26 20:04 ` H. Peter Anvin [this message]
2010-01-04 14:44 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B366C69.9010700@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdreier@cisco.com \
--cc=slyfox@inbox.ru \
--cc=slyich@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.