I've fixed that issue on my box about 6 month ago, I can't remember how I did that exactly. The core of it however was that the `locales` were defined in several places, like 2 or 3, and that one of them was inconsistent with the others. And I've justdeleted it.
Now my setting is, I have no local whatsoever, viz, I use `> LC_ALL="C.UTF-8"` and that's it. Only "spell check" is "US-EN".
Mar 20, 2022, 18:59 by inkbottle007@gmail.com:
I've fixed that issue on my box about 6 month ago, I can't remember how I did that exactly. The core of it however was that the `locales` were defined in several places, like 2 or 3, and that one of them was inconsistent with the others. And I've just deleted it.
Now my setting is, I have no local whatsoever, viz, I use `> LC_ALL="C.UTF-8"` and that's it. Only "spell check" is "US-EN".I will have to look into that, I was fiddling with "LC_ALL" recently to to a different issue and now it is set to LC_ALL=en_US.UTF-8, LC_ALL was unset
prior to that. Will report back when I try it.
Regards,
But, I really think LC_ALL="C.UTF-8", is already doing that.
How did you set LC_ALL to "C.UTF-8"? I tried adding LC_ALL="C.UTF-8"
to ~/.bash_profile but that seems to have no effect.
You need to export it. When you define an environment variable and do
not export it, it is not passed to sub-processes (like the one
executing the 'locale' command).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 21:24:43 |
Calls: | 10,390 |
Calls today: | 1 |
Files: | 14,061 |
Messages: | 6,416,983 |