Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
1
Found in [Package]
1.0.0
Issue ID
LOC-513
Regression
No
The Spanish language is not converted from code to "Spanish" in Xcode with the localization package
How to reproduce:
1. Open "Progetto localizzazioni.zip" project
2. Go to Build Settings (File>Build Settings)
3. Build for the iOS
4. Open the project in Xcode
5. Go to Unity-iPhone>Info.plist
6. Expand the Localization tab
Expected result: Item 3 is "Spanish"
Actual result: Item 3 is "es"
Reproducible with: 1.0.0 (2019.4.32f1, 2020.3.20f1, 2021.1.28f1), 1.0.5 (2019.4.32f1, 2020.3.20f1, 2021.1.28f1, 2021.2.1f1, 2022.1.0a13)
Could not test with: 1.0.0-pre.10 (No Localization tab also error shows "Unknown managed type referenced: \[Unity.Localization] UnityEngine.Localization.SmartFormat.Extensions.PersistentVariablesSource")
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Resolution Note:
This will not be fixed
Resolution Note (1.0.X):
This seems to be a limitation of xcode. The CFBundleLocalizations field has a very limited number of possible values according to the documentation here: https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundlelocalizations
If one of those values are used then the editor is able to show the language name in the Editor however this is purely cosmetic, it's still using the language codes in the actual file.
According to the property list reference documentation for CFBundleLocalizations:
Each entry in this property’s array is a string identifying the language name or ISO language designator of the supported localization.
We use ISO language designators for our Locales and populate them into the config file, if the language happen to be one of the Possible Values then they will get a language name label, however when the editor is switched to show the raw values you can see that they are all using language codes.
This does not prevent a built iOS app from having its supported languages correctly detected and you can see in the app settings that Spanish is displayed correctly.