public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kerin Millar <kerframil@fastmail.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] export LC_CTYPE=en_US.UTF-8
Date: Wed, 07 Aug 2013 23:27:30 +0100	[thread overview]
Message-ID: <5202C9D2.2050202@fastmail.co.uk> (raw)
In-Reply-To: <54F7DE7A-2D80-45D9-B373-63AE1A832B47@stellar.eclipse.co.uk>

On 07/08/2013 17:40, Stroller wrote:
>
> On 7 August 2013, at 13:41, Kerin Millar wrote:
>
>> On 06/08/2013 23:42, Stroller wrote:
>>>
>>> On 6 August 2013, at 14:04, Kerin Millar wrote:
>>>> ...
>>>> If undefined, the value of LC_COLLATE is inherited from LANG. I'm not sure that overriding it is particularly useful nowadays but it doesn't hurt.
>>>
>>> It's been a couple of years since I looked into this, but I'm given to believe that LANG should set all LC_ variables correctly, and that overriding them is frowned upon.
>>
>> As has been mentioned, there are valid reasons to want to override the collation. Here is a concrete example:
>>
>> https://lists.gnu.org/archive/html/bug-gnu-utils/2003-08/msg00537.html
>>
>> Strictly speaking, grep is correct to behave that way but it can be confounding.
>
> Linking also this answer, which you're aware of:
> https://lists.gnu.org/archive/html/bug-gnu-utils/2003-08/msg00600.html

Best practice will never be universally observed.

>
> This only goes to illustrate that you shouldn't be going overriding these willy-nilly without full awareness of why you're doing so and what you're doing.

It also served to illustrate the overall point I was making - that 
sticking to the C/POSIX collation is not without value as a safety 
measure. Naturally, I would expect anyone else to exercise their own 
judgement.

>
>
>>> I had to do this myself because, due to a bug, the en_GB time formatting failed to display am or pm. I believe this should be fixed now.
>>
>> Presumably:
>>
>> a) LANG was defined inappropriately
>> b) LANG was defined appropriately but LC_TIME was defined otherwise
>> c) LC_ALL was defined, trumping all
>
>
> I'm having trouble parsing this reply, but perhaps you might find the full bug description helpful. I wrote about 1000 words on the subject there last year.
>
> It is the top Google hit for "en_gb am pm bug": http://sourceware.org/bugzilla/show_bug.cgi?id=3768

OK.

--Kerin


  reply	other threads:[~2013-08-07 22:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 18:25 [gentoo-user] export LC_CTYPE=en_US.UTF-8 Chris Stankevitz
2013-08-05 18:53 ` Mike Gilbert
2013-08-05 18:57   ` Bruce Hill
2013-08-05 21:17     ` Mike Gilbert
2013-08-05 22:52   ` Chris Stankevitz
2013-08-05 23:25     ` [gentoo-user] " Kai Krakow
2013-08-06 13:04     ` [gentoo-user] " Kerin Millar
2013-08-06 13:24       ` Bruce Hill
2013-08-06 13:40         ` Kerin Millar
2013-08-06 14:26           ` Bruce Hill
2013-08-06 14:53             ` Kerin Millar
2013-08-06 15:51       ` Chris Stankevitz
2013-08-06 22:42       ` Stroller
2013-08-07 12:41         ` Kerin Millar
2013-08-07 16:40           ` Stroller
2013-08-07 22:27             ` Kerin Millar [this message]
2013-08-06 15:13     ` Mike Gilbert
2013-08-06 18:23       ` Chris Stankevitz
2013-08-07  0:58         ` Mike Gilbert

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=5202C9D2.2050202@fastmail.co.uk \
    --to=kerframil@fastmail.co.uk \
    --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