All,
Tonight's update on 32-bit Bullseye on a Pi Zero 2 W produces several warnings related to language settings that seems to mismatch US and GB language files. The curious output from the update was:
First, if LC_CTYPE = "en_US.UTF-8" is set, why would the perl fallback select "en_GB.UTF-8" - that seems like a distinct mismatch. If any one of LANGUAGE, LC_ALL, or LC_CTYPE is set, shouldn't the fallback be that?
Note: there is no similar warning issued by the same update on 64-bit Bullseye on a second Pi Zero 2 W.
This system was installed less than a year ago with the PiOS installer, should there be additional settings made by the installer on install?
Granted, none of this is a show-stopper, but it just seems that it should at least be consistent. What say the experts?
Tonight's update on 32-bit Bullseye on a Pi Zero 2 W produces several warnings related to language settings that seems to mismatch US and GB language files. The curious output from the update was:
Code:
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u10) ...perl: warning: Setting locale failed.perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE = "en_US.UTF-8", LC_COLLATE = "C", LANG = "en_GB.UTF-8" are supported and installed on your system.perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").Note: there is no similar warning issued by the same update on 64-bit Bullseye on a second Pi Zero 2 W.
This system was installed less than a year ago with the PiOS installer, should there be additional settings made by the installer on install?
Granted, none of this is a show-stopper, but it just seems that it should at least be consistent. What say the experts?
Statistics: Posted by drankinatty — Tue Sep 03, 2024 4:27 am