Why is yay now speaking Portuguese with me
-
Ah- because I removed the en_US.UTF-8 locale
Why can't yay use the en_GB.UTF-8 locale and ehy does it default to Portuguese??
@MagicLike@soc.sekundenklebertransportverbot.de I mean I'm sure it can if you specify
-
@MagicLike@soc.sekundenklebertransportverbot.de
Check installed locales and what your Lang or lc_* variables say.@kura installed locales are
C
C.utf8
de_DE.utf8
en_GB.utf8
en_US.utf8
POSIX -
@kura installed locales are
C
C.utf8
de_DE.utf8
en_GB.utf8
en_US.utf8
POSIX@kura my LC_ variables are all set to de_DE.UTF-8, except LC_ALL
-
@kura my LC_ variables are all set to de_DE.UTF-8, except LC_ALL
@MagicLike@soc.sekundenklebertransportverbot.de @kura@hai.z0ne.social de_DE.UTF-8 as opposed to utf8?
-
@kura my LC_ variables are all set to de_DE.UTF-8, except LC_ALL
@MagicLike@soc.sekundenklebertransportverbot.de I hope lc_all is empty. Or else it will overwrite everything else.
-
Ah- because I removed the en_US.UTF-8 locale
Why can't yay use the en_GB.UTF-8 locale and ehy does it default to Portuguese??
@MagicLike tbh id never recommend removing en_US tbh, some things are hard coded last time i checked (both Gnome Terminal and Half Life refused to start without it, not sure if it was a env var issue or not but still) -
@MagicLike@soc.sekundenklebertransportverbot.de I hope lc_all is empty. Or else it will overwrite everything else.
@kura yes it is empty, sorry forgot to write that
-
@MagicLike tbh id never recommend removing en_US tbh, some things are hard coded last time i checked (both Gnome Terminal and Half Life refused to start without it, not sure if it was a env var issue or not but still)
@null yeah I noticed
-
@MagicLike@soc.sekundenklebertransportverbot.de @kura@hai.z0ne.social de_DE.UTF-8 as opposed to utf8?
@darkphoenix @kura yeah it seems they both mean the same because in
/etc/locale.genit is .UTF-8, but when I runlocale --all-localesit is .utf8 -
@MagicLike@soc.sekundenklebertransportverbot.de I mean I'm sure it can if you specify
@darkphoenix apparently it is a long lasting issue, that yay does not use the correct locale and does not adjust correctly to local changes, the GitHub issue is open since 2023 >.>
-
@darkphoenix apparently it is a long lasting issue, that yay does not use the correct locale and does not adjust correctly to local changes, the GitHub issue is open since 2023 >.>
@darkphoenix seems like yay does not ise the
LANGvar, but rather theLANGUAGEvar
-
@darkphoenix seems like yay does not ise the
LANGvar, but rather theLANGUAGEvar@darkphoenix but for now I am not hoing to fuck around with it, but rather want it to work lol
