public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Locale check in python_pkg_setup()
Date: Sat, 31 Jul 2010 17:39:27 -0400	[thread overview]
Message-ID: <m31vajmiu0.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <4C530291.2010100@gentoo.org> ("Paweł Hajdan, Jr."'s message of "Fri, 30 Jul 2010 09:49:21 -0700")

>>>>> "PH" == Paweł Hajdan, <phajdan.jr@gentoo.org> writes:

PH> Another thing we can consider is making UTF8 the default setup in
PH> Gentoo. I think most people (including me) don't care whether it's
PH> C or UTF8 as long as it works.

Forcing utf-8 will only be reasonable when there is a C.UTF-8 and/or
a POSIX.UTF-8 locale.

That should be done upstream in glibc, but were they to refuse then
Gentoo should add it to the glibc ebuild.

The language_country locales are just wrong for root.  They are often
broken (locales like en_US force case-insensitive colation, meaning that
a command such as 'rm [a-z]*' will unlink(2) 'Makefile' and similar files
which one would not expect to match) and cause bugs.

In fact, glibc's insistance that C and POSIX are ascii rather than raw
unspecified eight bit is itself a bug.

Utf8 is nice, but forcing the lang_country locales on root is not.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6



  parent reply	other threads:[~2010-07-31 21:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 23:16 [gentoo-dev] Locale check in python_pkg_setup() Arfrever Frehtes Taifersar Arahesis
2010-07-29 23:20 ` "Paweł Hajdan, Jr."
2010-07-30  2:29   ` Arfrever Frehtes Taifersar Arahesis
2010-07-30  3:05     ` "Paweł Hajdan, Jr."
2010-07-30  0:13 ` [gentoo-dev] " Jonathan Callen
2010-07-30  2:32   ` Arfrever Frehtes Taifersar Arahesis
2010-07-30  2:36 ` [gentoo-dev] " Brian Harring
2010-07-31 14:44   ` Arfrever Frehtes Taifersar Arahesis
2010-07-31 19:49     ` Alec Warner
2010-07-31 20:10       ` Arfrever Frehtes Taifersar Arahesis
2010-07-31 20:25         ` Petteri Räty
2010-08-02 21:02           ` Arfrever Frehtes Taifersar Arahesis
2010-08-02 21:40             ` Harald van Dijk
2010-07-30  3:15 ` Krzysztof Pawlik
2010-07-30  3:48   ` Brian Harring
2010-07-30 16:49     ` "Paweł Hajdan, Jr."
2010-07-30 18:45       ` Brian Harring
2010-07-31 21:39       ` James Cloos [this message]
2010-07-31 22:04         ` Mike Frysinger
2010-07-31 22:14           ` James Cloos
2010-07-31 22:53             ` Mike Frysinger
2010-07-31 23:30         ` [gentoo-dev] " Jonathan Callen
2010-08-05 14:00           ` James Cloos
2010-07-30 16:05 ` [gentoo-dev] " Harald van Dijk
2010-07-31  3:37 ` Mike Frysinger
2010-08-02 21:18 ` Arfrever Frehtes Taifersar Arahesis
2010-08-02 21:40   ` Mike Frysinger
2010-08-02 22:08   ` Jeroen Roovers
2010-08-02 22:13   ` Jeroen Roovers
2010-08-03  0:58   ` Brian Harring

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=m31vajmiu0.fsf@carbon.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=gentoo-dev@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