Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.64f1
6000.3.1f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-130673
Regression
No
Indic languages are displayed incorrectly when using TextMeshPro or Legacy Text
How to reproduce:
1. Open the attached “IN-125292_HindiTextIssue” project
2. Open the “SampleScene“
3. In the Hierarchy tab, expand the dropdown of the “Canvas” GameObject
4. Select the “Text (TMP)” GameObject
5. In the Inspector tab, navigate to the “TextMeshPro - Text (UI)” component
6. Make sure the Font Features setting is set to “liga“ in the Extra Settings tab
7. Paste “वृत्तचित्र” into the “Text Input” field
8. Observe the Game window
Expected result: The word “वृत्तचित्र” appears as expected in the Game window
Actual result: The word “वृत्तचित्र” is distorted in the Game window
Reproducible with: 2022.1.0a5, 6000.0.64f1, 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Reproducible on: macOS 15.3.2 (24D81) (M1 Max)
Not reproducible on: No other environments tested
Notes:
- Reproducible in Player
- “Hindi and Bengali Distortion.png” attached, better illustrates the difference between the expected and actual result
- Text appears incorrect despite using the “liga” Font Feature
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:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.