Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.5.4
Issue ID
LOC-1211
Regression
No
Languages with non-Latin alphabets do not appear in Localization table when imported through CSV files
How to reproduce:
1. Open the attached “IN-100615” project
2. Open the “Localization Tables” tab and create a new String Table Collection with all locales selected
3. Click on Import > CSV in the upper right corner and import the attached “IN-100615_CSV.csv” file
4. Observe the result
Expected result: Text appears in all boxes of the table
Actual result: Text with non-Latin alphabets does not appear
Reproducible with: 1.0.4 (2022.3.32f1), 1.5.4 (2022.3.62f1, 6000.0.48f1, 6000.1.3f1, 6000.2.0a10)
Could not test with: 1.0.3 (2022.3.32f1) (no localization window functionality)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Note: Tested with Chinese, Japanese, Korean, Arabic, Hindi and Russian
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Hi,
Thank you for your bug report regarding Chinese values not being imported from the CSV.
After closer inspection, I found that the issue lies with the column headers in your CSV file. When importing, the system matches each column to a language by checking the column header. In your case, the column header for Chinese is currently set to "(Simplified)(zh)", which the system is unable to recognize.
To resolve this issue, please update the column header to "Chinese (Simplified)(zh-Hans)". Once updated, the import should work as expected.
Kind regards,
Karl Jones
Staff Software Engineer