Search Issue Tracker
Feature Request
Feature Request in 2023.2.X
Votes
0
Found in
2021.3.19f1
2022.2.7f1
2023.1.0b4
2023.2.0a2
Issue ID
UUM-27244
Regression
No
Khmer is displayed wrong when used in the Text field
How to reproduce:
1. Open the attached “Text.zip” project
2. Open the “SampleScene” Scene (Assets > Scenes > SampleScene)
3. Open the Game window and observe the result
Expected result: “សួស្តី” text is visible
Actual result: More text than "សួស្តី" is visible
Reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.7f1, 2023.1.0b4, 2023.2.0a2
Reproduced on:
macOS 12.4 (Intel)
Windows 10 (user’s info)
Notes:
Reproducible in the Editor and Standalone Player
Reproducible with TextMeshPro (3.0.6, 4.0.0-pre.1) and Legacy Text
In the Inspector window, there are just squares or nothing in the text fields
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
TextMesh Pro currently has limited support for OpenType Font Features. We currently only support kerning, ligatures and marks.
We are actively working on a solution to bring full OpenType Font Features to solve this issue.
Resolution Note (2023.2.X):
TextMesh Pro currently has limited support for OpenType Font Features. We currently only support kerning, ligatures and marks.
We are actively working on a solution to bring full OpenType Font Features to solve this issue.