Yes, this is what I confirmed earlier.
Are you absolutely certain about this?
Is it working now?
Yes/No.
I just wanted to say that editing root files is not always useful because it is prone to errors.
All the Wikis are always confusing because there is simply too much information in one place.
1 Like
For testing purposes, I have created a VM with i3. I can confirm that I was able to install with C.UTF-8 selected for LANG and locale and it stayed after reboot.
What I had suggested in a previous post, was upon setting LANG, everything else then defaults to the en_US.UTF-8 for all (or whatever other LANG had been set), which is what I had thought that C was supposed to do.
I have now reset it all back to C and rebooted without problems.
I did all of the above using localectl followed with sudo locale-gen without any problems. Both locale and localectl output the same results. I tried several other LANG settings as well (after uncommenting them in /etc/locale.gen and the result is the same. All locale settings default to the new language setting.
Edit: In other words, I cannot get LANG set to US and everything else set to C. Itās either, or, not both and.
1 Like
So the other way around?
With the best will in the world, I donāt see any sense in it except for the AM/PM time display. Above all, I donāt believe that this can be selected during installation! This has already been asked/mentioned above. Under C.UTF-8 the clock is in any case in 24 hour mode.
I would first try what I have already written above. But there is a bit of work involved.
I would try something like that:
sudo localectl set-locale LC_MESSAGES=C.UTF-8 LANG=en_US.UTF-8
and if itās about the time, maybe change/add
LC_TIME=C.UTF-8
Tip: You can find all LC entries with the locale command. Please remember the exclamation marks or better do it with localectl
From here on Iām out because I canāt understand it anymore. 
You donāt believe what can be selected during installation? If you are referring to C, it can beā¦
And with C set, simply running sudo localectl set-locale LANG=en_US.UTF-8 then running sudo locale-gen sets everything to US. Returning LANG to C, also does the reverse. Iāve tested it multiple times in a VM today.
The other user explained in a post above why they want it set to C.
I do agree, localectl is easier, but editing the config file does work.
1 Like
i kinda got it into an acceptable state. all it set to C which is something iām fine with.
1 Like
yes, that is where i believed i made a mistake. i set both to en_US even though i intended the first one to be en_US and the other one C (which by my understanding from this thread would give the same result? before this i didnāt see anywhere that it would conform to whatever LANG it set to)
i personally prefer editing the configs as i find it more readable. i also prefer doing it the ātraditionalā way if possible instead of relying on some systemd command.
setting LC_ALL=C.UTF-8 gives me good results. the system language is in english and the dates/times are sensible so i think iāll keep it that way.
1 Like
I understand where youāre coming from. For almost everything that I reasonably can, I use traditional config files. I like being able to see everything at once and understand the correlation with other things going on.
This situation comes more down to convenience. I first learned how to use localectl before I knew about the config file. For awhile, I did a combination between the two and sometimes it worked and sometimes not.
Iād have to look back where I read it earlier today where I learned that LANG sets everything else. The 3 main things I looked at were Arch wiki, Arch forum, and Linux man pages. After experimenting with the VM is where I confirmed it.
Best of luck and Iām glad you were able to at least get it to a place where you want it to be and itās not Americanized. 
1 Like