mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: "H. Peter Anvin" <hpa@zytor.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: Fri, 25 Dec 2009 22:58:28 -0800	[thread overview]
Message-ID: <adaljgqz0ff.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <4B356730.2080401@zytor.com> (H. Peter Anvin's message of "Fri, 25 Dec 2009 17:30:24 -0800")


 > > 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.

  reply	other threads:[~2009-12-26  6:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-25 17:13 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 [this message]
2009-12-26 20:04     ` H. Peter Anvin
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=adaljgqz0ff.fsf@roland-alpha.cisco.com \
    --to=rdreier@cisco.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome