Search Issue Tracker
Active
Votes
1
Found in
6000.0.62f1
6000.2.13f1
6000.3.0f1
6000.4.0a5
6000.5.0a1
Issue ID
UUM-128220
Regression
No
TextMeshPro ligatures broken when Font Style setting is changed from “Lowercase” to “Uppercase”
How to reproduce:
1. Open the attached “IN-122021“ project
2. Observe the Game window. Notice that the letters “L” and “A” are connected at the baseline
3. In the Hierarchy window, select “Text (TMP)” GameObject
4. In the Inspector, in the “TextMeshPro - Text (UI)” component, change Text Input to “play lf tw”
5. Change Font Style to “Uppercase”
6. Observe the Game window
Expected result: The letters “L” and “A” are connected at the baseline
Actual result: The letters “L” and “A” are not connected at the baseline
Reproducible with: 2023.2.0a14, 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a1
Could not test with: 2022.1.0a5, 2023.2.0a8 (The “Extra Settings” tab does not have a Font Features dropdown with the “liga” setting)
Reproducible on: macOS 15.3.2 (24D81) (M1 Max), Windows 11 (10.0.26100) X64 (Tested by the reporter)
Not reproducible on: No other environments tested
Note: Reproducible in Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some Build Profile settings do not remain checked when launching a project without the /Library folder through the command line
- TextMeshPro gradient tags render as literal text when using a font that contains only a part of the ASCII character set
- Small rectangles appearing in the corner of title text in Editor when System Font and Bitmap are selected in preferences
- The shortcut character is typed into the name field when a [Shift + <any alphanumeric key>] shortcut is used to create the asset from "Asset/Create"
- TextMeshPro ligatures broken when Font Style setting is changed from “Lowercase” to “Uppercase”
Add comment