when mounting some device,I noticed that some character is displayed incorrectly
I do dpkg-reconfigure locales , checked en_US.UTF-8 , everything is right
Why ship OSMC without any UTF-8 locales, at least en_US.UTF-8 [Raspberry Pi]
Because en_US is not appropriate for most people.
When you log in for the first time via SSH, your locales will be autogenerated based on the connecting client if it exposes it.
I didn’t remember that it did generate or ask me to generate new locales when I connect to OSMC via xShell
does OSMC/kodi list filenames based on system's locales?
even though ,if it has nothing to do with terminal encoding and locales,If it wants to display correct filenames, should The right locales exits in system?
Ship with at least one UTF8 locale would be OK, I .think.
@sam_nazarko
what does Vero 2 do to deal with customers’s various locales across the world?
We ship with all locales, they are just generated on demand.
If none were generated for you it means your SSH client does not forward it properly
Locales can always be manually configured however