| 1 |
On 7 August 2013, at 13:41, Kerin Millar wrote: |
| 2 |
|
| 3 |
> On 06/08/2013 23:42, Stroller wrote: |
| 4 |
>> |
| 5 |
>> On 6 August 2013, at 14:04, Kerin Millar wrote: |
| 6 |
>>> ... |
| 7 |
>>> 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. |
| 8 |
>> |
| 9 |
>> 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. |
| 10 |
> |
| 11 |
> As has been mentioned, there are valid reasons to want to override the collation. Here is a concrete example: |
| 12 |
> |
| 13 |
> https://lists.gnu.org/archive/html/bug-gnu-utils/2003-08/msg00537.html |
| 14 |
> |
| 15 |
> Strictly speaking, grep is correct to behave that way but it can be confounding. |
| 16 |
|
| 17 |
Linking also this answer, which you're aware of: |
| 18 |
https://lists.gnu.org/archive/html/bug-gnu-utils/2003-08/msg00600.html |
| 19 |
|
| 20 |
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. |
| 21 |
|
| 22 |
|
| 23 |
>> 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. |
| 24 |
> |
| 25 |
> Presumably: |
| 26 |
> |
| 27 |
> a) LANG was defined inappropriately |
| 28 |
> b) LANG was defined appropriately but LC_TIME was defined otherwise |
| 29 |
> c) LC_ALL was defined, trumping all |
| 30 |
|
| 31 |
|
| 32 |
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. |
| 33 |
|
| 34 |
It is the top Google hit for "en_gb am pm bug": http://sourceware.org/bugzilla/show_bug.cgi?id=3768 |
| 35 |
|
| 36 |
Stroller. |
Archives