This is the first I've heard of any advice to avoid LC_ALL, and I wonder what is prompting that advice.
It would be a pain to set every other LC_* environment variable to en_US.utf8, and POSIX says there should be no point to doing so, as POSIX requires the painful approach to have the same effect as simply setting LC_ALL. See the POSIX spec for internationalization variables in:
Briefly, POSIX says that setting LC_ALL to a value should have the same effect as setting the other LC_* variables to that value. It should also have the same effect as setting LANG to that value while leaving all LC_* variables unset.
If the snap packaging for Chromium and Firefox doesn't do that, then it's a bug in the snap packaging that should get fixed.
This is the first I've heard of any advice to avoid LC_ALL, and I wonder what is prompting that advice.
It would be a pain to set every other LC_* environment variable to en_US.utf8, and POSIX says there should be no point to doing so, as POSIX requires the painful approach to have the same effect as simply setting LC_ALL. See the POSIX spec for internationaliz ation variables in:
https:/ /pubs.opengroup .org/onlinepubs /9699919799/ basedefs/ V1_chap08. html#tag_ 08_02
Briefly, POSIX says that setting LC_ALL to a value should have the same effect as setting the other LC_* variables to that value. It should also have the same effect as setting LANG to that value while leaving all LC_* variables unset.
If the snap packaging for Chromium and Firefox doesn't do that, then it's a bug in the snap packaging that should get fixed.