.NET Core Locale Missing under Linux System

[hajuuk]

When I try to deploy a ASP.NET Core application to a Linux system, I figured out the localization may have some critical issue.

I using following code in .NET Core Console application to isolate the issue, by list all available cultures.

            foreach (var culture in CultureInfo.GetCultures(CultureTypes.AllCultures))
            {
                Console.WriteLine(culture.Name);
            }

Then, the result have lots of differences, not just missing zh-CN or zh-HK.

This file is executed and fetched under Windows 10 1809
Windows.txt

This file is executed and fetched under Linux 4.9.0-8-amd64 dotnet/corefx#1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux
Linux.txt

I can use zh-Hans to replace zh-CN, but it would missing some other things, like DateTime format. Also, most npm package are using zh-CN as default Simp. Chinese language code, so it may also missing the localization data for such npm package, like Bootstrap DatetimePicker, if I directly using Culture infomation for js localization.

Is there have any existing solution for that case? Thanks

[hajuuk]

It might OS dependency, however, I found the debian it self support zh-CN, zh-HK and aa.

Here is the list:

cat /usr/share/i18n/SUPPORTED

Result.txt

[tarekgh]

@hajuuk .NET core is using the underlying OS for globalization. On Linux we use ICU library for the globalization support. When enumerating the locales, we use ICU to do so. ICU has the notion of some aliased locales which are not reported in the enumeration but still can use it (through the alias name). So, such locales will not show in the list returned by CultureInfo.GetCultures but you can still do CultureInfo.GetCultureInfo("zh-CN") and that should still work. We are trying to have a parity with the underlying OS and you can expect some differences between OS's but in general the differences is going smaller and smaller as Windows now using the same source of globalization data.

To summarize, the missing locales in the enumeration doesn't mean you cannot use such locale and the .NET Core behavior is by design globalization behave as the underlying OS as .NET not really carrying any globalization data.

I am closing this issue but feel free to reply back with any question you have and thanks for your report.