On Sunday, 13 June 2021 15:11:18 BST Dr Rainer Woitok wrote: > All, > > On Sunday, 2021-06-13 15:39:46 +0200, I myself wrote: > > ... > > > > > > $ sudo locale > > > > LANG=en_GB.utf8 > > > > ... > > > > Erm, is there a difference between "*.utf8" and "*.UTF-8"? Does case > > matter? > > Apparently yes. At least for Perl or anything else used by Portage. > Running my package upgrade script again after setting > > $ export LANG=en_GB.UTF-8 > > just succeeded. "As soon as you're doing it right, it just works". :-) > But what exactly is the difference? > > Sincerely, > Rainer
If you have a look at the comments in /etc/locale.gen it explains where to find suitable notation for locale name, charset, and it also provides a default list of supported combinations: /usr/share/i18n/SUPPORTED In there we find: $ grep -i en_gb /usr/share/i18n/SUPPORTED en_GB.UTF-8 UTF-8 en_GB ISO-8859-1 I recall in the past having had a similar problem and as you say, once you set it up correctly it just works. :-) I don't know what the difference is between lower/upper case notation for the charset, but having set it up in capitals seems to work here. Note, I don't have any lower case charset in / etc/locale.gen. $ eselect locale list Available targets for the LANG variable: [1] C [2] C.utf8 [3] POSIX [snip ... ] [7] en_GB [8] en_GB.iso88591 [9] en_GB.utf8 [10] en_US [11] en_US.iso88591 [12] en_US.utf8 [13] en_GB.UTF-8 * [ ] (free form)
signature.asc
Description: This is a digitally signed message part.
