Bug (Case 1376680) Localization: Hindi system language not detected

Unity 2019.4.29f1, Localization 1.0.4, Addressables 1.19.6

The Localization package does not detect if Hindi is used as system language on an Android device. The Localization system uses English instead.

Reproduce

1. Open attached project
2. Open "File > Build Settings..." and switch to Android build target
3. Open "Window > Asset Management > Addressables > Groups"
4. Click in Addressables Groups window "Build > New Build > Default Build Script"
5. Click "File > Build and Run" and run the app on your Android phone
6. On your Android phone, open Language Settings and activate "Hindi" language
7. Restart app on your Android phone

Actual
The text displays "English"

Expected
The text displays "Hindi"

Note
I don't know what other languages are not detected and I also don't know what other platforms have this problem. It would be good if you would perform this test with all locales that the Localization system supports and different platforms (Android and iOS at least).

 

Thank you, that's really great. Do you happen to know if it's the same thing why Hindi isn't working on iOS?

 

Hey Karl, thank you for the help.

I can't get it to work. I'm testing on a Samsung Galaxy S6 with Android 7.0. When I set the system language to Hindi, the attached project still displays English. It does work with German though, but it doesn't work with Hindi.

What am I doing wrong?

 

Yes it does display the Hindi app name.

 

It's 2019.4, I can test it for you with 2021.2, but I ultimately need it to work in 2019.4.

 

I tested it with 2021.2.1f1 and it's the same problem. The app name is localized, but in the Player it displays English instead of Hindi. It does work with other languages, such as German, just fine though.

 

Unity 2021.1.1f1, Localization 1.0.4, Addressables 1.19.9, Samsung Galaxy S6, Android 7.0

Application.systemLanguage

does not have a Hindi enumerated member, so it returns

Unknown

. CultureInfo methods don't work on Android and iOS as mentioned in the other thread, so they return

""

(empty string) for

CultureInfo.Name

and

"iv"

for

CultureInfo.TwoLetterISOLanguageName

.

Code (CSharp):

1. var sb = new System.Text.StringBuilder();
2. sb.Append($"Application.systemLanguage: {Application.systemLanguage}\n");
3. sb.Append($"CurrentThread.CurrentCulture: {System.Threading.Thread.CurrentThread.CurrentCulture.Name}\n");
4. sb.Append($"CurrentThread.CurrentUICulture: {System.Threading.Thread.CurrentThread.CurrentUICulture.Name}\n");
5. sb.Append($"CultureInfo.CurrentCulture: {System.Globalization.CultureInfo.CurrentCulture.Name}\n");
6. sb.Append($"CultureInfo.CurrentUICulture: {System.Globalization.CultureInfo.CurrentUICulture.Name}\n");
7. m_Text.text = sb.ToString();

Here is a screenshot with Hindi system language:



Here is a screenshot with German system language:

 

I think there is an issue with CurrentCulture info (on iOS and Android) in Unity in general. For that reason I had to write my custom language selector as Localizations' selector in package doesnt work properly.

see also : https://forum.unity.com/threads/cul...-invariant-language-invariant-country.554941/

 

Thank you for the reply.

According to your screenshot, your fallback is Hindi. So even when "System Locale Selector" doesn't detect the system Hindi language, which is what I reported, the "Specific Locale Selector" will set it to Hindi regardless.

In the project I submitted, the "Project Locale Identifier" and "Specific Locale Selector" are both "English" instead of Hindi. Please use the project I attached to the bug-report without any modifications (other than adding the Android App Info metadata).

I'm able to reproduce this issue across different devices Android/iOS with different OS versions. All I have to do to reproduce the issue is to open the project from Case 1376680, build for Android and run it on a real device (not an emulator).

 

https://issuetracker.unity3d.com/is...t-is-the-system-language-on-an-android-device

 

Hey Karl, I saw the issue is fixed in 1.1.0. Thank you! I wonder if it just works or requires to upgrade Unity. I'm using 2019.4.20f1.