On Sat, 7 May 2022, Adam Borowski wrote:
> As of Bookworm, ancient encodings are no longer supported. There are
?
> But, as glibc still considers unset locale to mean "C" rather than
> "C.UTF-8", _something_ must set these variables. Debian-installer does
There's talk to chage that in glibc-in-Debian at least.
> that, but bare debootstrap does not, and neither do some other ways of
> installing Debian. Baring explicit configuration by the user, the
> locale will remain unset.
Debian officially only supports d-i though, but getting C as default
is not a bad thing compared to other available options.
> Thus, let's add putenv("LANG=C.UTF-8") to pid 1; further startup will
> usually overwrite that with whatever values are configured -- possibly
> "C" to go back to the old state.
Not exactly: if explicitly unconfigured to keep C, it’ll change.
It will change in a compatibl-ish way, sure (which is why I proposed
C.UTF-8 to be created about nine years ago in the first place), but
things can break (tr -dc '[[:alpha:]]' changes meaning, for example).
> As systemd does define LANG=C.UTF-8, I'm not hopeful the default will
They do? Ugh. Of course they do whatever suits Poettering’s laptop.
I’m personally not convinced in favour of this switch, but, yeah,
let’s do this for inner consistency in Debian.
I’d put it into /etc/rc, not the init binary, though, but I see that
such a thing doesn’t exist… and I guess it would not handle whatever
is run from inittab, so… probably, yeah.
I was just writing about calling init scripts, but my cleanenv script
has been using C.UTF-8 in LC_ALL for 15 months already, too… so, okay.
Not making much sense this late in the night? IF so, sorry.
gn8,
//mirabilos
--
Yes, I hate users and I want them to suffer.
-- Marco d'Itri on gmane.linux.debian.devel.general
