Search Issue Tracker
Feature Request
Votes
0
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
Issue ID
UUM-52681
Regression
No
Nepali characters are rendered using other language characters
How to reproduce:
1. Open the user’s attached “nepal-language.zip” project
2. Open “NepalLanguage” Scene (Assets > Scenes)
3. Observe the text of “Text (Legacy)” GameObject in the Scene, Game or Inspector window
Expected result: Text is "पिठिउ"
Actual result: Text is not "पिठिउ"
Reproducible with: 2021.3.3f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Notes:
- TextMeshPro is showing squares instead of a word
- reproducible in the Editor and Standalone player (macOS)
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
This workflow is not currently supported. Language detection and using different glyphs according to the language is not a feature supported by our current Text system. However, we are actively working on addressing this limitation in an upcoming version of Unity for UITK.