From: Mike Edenfield <kutulu@kutulu.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] locale issue to clean up
Date: Mon, 08 Dec 2008 12:03:34 -0500 [thread overview]
Message-ID: <493D5366.4070802@kutulu.org> (raw)
In-Reply-To: <5bdc1c8b0812071910l1beab0e8s6d6124954689a677@mail.gmail.com>
Mark Knecht wrote:
> You may be correct about setting all of this in 02locale. I noticed
> that the Gentoo formatting stuff for vi is treating LC_ALL and
> LC_COLLATE differently than LINGUAS. The manual seems to say set
> system wide stuff in 02locale and user stuff in your own account.
They are different.
LINGUAS is a build-time hint for localized programs that lists which
languages you want translations for. It has no effect at run-time other
than ensuring that your selected languages are available.
The LC_* variables, and LANG, are run-time settings that tell the C
library which locale to use. LC_COLLATE, for example, tells vi how to
sort things alphabetically.
Just as an aside, I see frequent warnings not to set LC_ALL because it's
"dangerous", but that seems like a vast overreaction to me. LC_ALL is a
global setting that overrides all of the other LC_ variables with a
single setting. The "danger" is that you cannot then individually
override the behavior, say to use a different currency or sorting
format, but IMO the people who need to do that are the exception, and
would clearly know how to do it.
For a single user system with a single locale where all the LC_*
variables have the same value anyway, setting LC_ALL to "en_US" and
settings the other half-dozen LC_* variables to "en_US" has the same effect.
next prev parent reply other threads:[~2008-12-08 17:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 21:35 [gentoo-user] locale issue to clean up Mark Knecht
2008-12-07 21:55 ` Dale
2008-12-07 22:10 ` Mark Knecht
2008-12-07 23:29 ` Dale
2008-12-07 23:45 ` Mark Knecht
2008-12-08 0:06 ` Dale
2008-12-08 0:12 ` Mike Edenfield
2008-12-08 0:04 ` Mike Edenfield
2008-12-07 23:17 ` Mark Knecht
2008-12-08 0:10 ` Mike Edenfield
2008-12-08 0:42 ` Mark Knecht
2008-12-08 1:14 ` smallnow
2008-12-08 3:10 ` Mark Knecht
2008-12-08 5:32 ` Mark Knecht
2008-12-08 16:32 ` Mark Knecht
2008-12-08 17:03 ` Mike Edenfield [this message]
2008-12-08 16:01 ` Mike Edenfield
2008-12-08 1:19 ` Willie Wong
2008-12-08 2:58 ` Mark Knecht
2008-12-08 17:24 ` Mick
2008-12-08 18:50 ` Mark Knecht
2008-12-08 19:02 ` Dale
2008-12-08 19:10 ` Mike Edenfield
2008-12-09 18:33 ` Mark Knecht
2008-12-08 16:58 ` Mike Edenfield
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=493D5366.4070802@kutulu.org \
--to=kutulu@kutulu.org \
--cc=gentoo-user@lists.gentoo.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