Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
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
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.