| 1 |
On Sunday, 13 June 2021 15:11:18 BST Dr Rainer Woitok wrote: |
| 2 |
> All, |
| 3 |
> |
| 4 |
> On Sunday, 2021-06-13 15:39:46 +0200, I myself wrote: |
| 5 |
> > ... |
| 6 |
> > |
| 7 |
> > > > $ sudo locale |
| 8 |
> > > > LANG=en_GB.utf8 |
| 9 |
> > > > ... |
| 10 |
> > |
| 11 |
> > Erm, is there a difference between "*.utf8" and "*.UTF-8"? Does case |
| 12 |
> > matter? |
| 13 |
> |
| 14 |
> Apparently yes. At least for Perl or anything else used by Portage. |
| 15 |
> Running my package upgrade script again after setting |
| 16 |
> |
| 17 |
> $ export LANG=en_GB.UTF-8 |
| 18 |
> |
| 19 |
> just succeeded. "As soon as you're doing it right, it just works". :-) |
| 20 |
> But what exactly is the difference? |
| 21 |
> |
| 22 |
> Sincerely, |
| 23 |
> Rainer |
| 24 |
|
| 25 |
If you have a look at the comments in /etc/locale.gen it explains where to |
| 26 |
find suitable notation for locale name, charset, and it also provides a |
| 27 |
default list of supported combinations: |
| 28 |
|
| 29 |
/usr/share/i18n/SUPPORTED |
| 30 |
|
| 31 |
In there we find: |
| 32 |
|
| 33 |
$ grep -i en_gb /usr/share/i18n/SUPPORTED |
| 34 |
en_GB.UTF-8 UTF-8 |
| 35 |
en_GB ISO-8859-1 |
| 36 |
|
| 37 |
I recall in the past having had a similar problem and as you say, once you set |
| 38 |
it up correctly it just works. :-) I don't know what the difference is |
| 39 |
between lower/upper case notation for the charset, but having set it up in |
| 40 |
capitals seems to work here. Note, I don't have any lower case charset in / |
| 41 |
etc/locale.gen. |
| 42 |
|
| 43 |
$ eselect locale list |
| 44 |
Available targets for the LANG variable: |
| 45 |
[1] C |
| 46 |
[2] C.utf8 |
| 47 |
[3] POSIX |
| 48 |
[snip ... ] |
| 49 |
[7] en_GB |
| 50 |
[8] en_GB.iso88591 |
| 51 |
[9] en_GB.utf8 |
| 52 |
[10] en_US |
| 53 |
[11] en_US.iso88591 |
| 54 |
[12] en_US.utf8 |
| 55 |
[13] en_GB.UTF-8 * |
| 56 |
[ ] (free form) |
Archives