Chinese, then Chinese content will render correctly with correct Chinese system font PingFang.Īnother issue that is also very important is that Chinese (Simplified or Traditional), Korean and Japanese share amount of the same characters but written differently. It's different on macOS or iOS however, if you set a system locale order as 1. However UWP apps using the new UI framework (like Unigram, Intel Command Centre etc) behave correctly if setting Chinese/Korean as secondary language. This is largely true for traditional Win32 programmes, like Chrome, Edge, Explorer.exe, etc. Many programmes runs properly only in designed locales, not that programmes run well in any locale.Ĭhinese/Korean rendered incorrectly on English UI because system hardcoded a font fallback, which put Japanese font first, regardless of how languages are ordered in the Settings.
I believe Windows's approach is localisation not globalisation.