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

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.


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

Stroller.


Reply via email to