Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0f2
Issue ID
1154280
Regression
No
[Scripting] SystemLanguage.Language returns a different value from its property.enumValueIndex for values higher than 18
How to reproduce:
1. Open user-submitted project (SystemLanguageBugReport)
2. Create a new Language Package asset by clicking Assets > Create > Language Package
3. Attach the LanguageMonoBehaviour.cs to any GameObject
4. Assign to the created Language Package to the 'Package' variable
5. Select the Language Package asset, select 'Icelandic' language and click 'Log property Enum value'
6. Enter Play Mode and compare the Console output
Expected result: SystemLanguage.Language and property.enumValueIndex return the same value
Actual result: property.enumValueIndex value is higher than SystemLanguage.Language value
Reproducible with: 2017.4.27f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3
Notes:
Values returned match correctly for languages Afrikaans-Hungarian
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "DateTime.Now" in the UK timezone does not adjust when the British Summer Time is active
- "Unsupported source texture format (7) in ComputeNextMipLevel" error is shown and the texture atlas is corrupted when the texture format "RGB Compressed ETC2 4bits" is selected
- The label that uses data binding is no longer updated at runtime when `INotifyBindablePropertyChanged` reloads updates of the VisualTreeAsset in UIDocument
- HDRP Graphics "High Quality Line Rendering" is missing a documentation link
- HDRP Graphics "Screen Space Global Illumination" has a link to a wrong documentation
Resolution Note (2020.1.X):
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.