Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
2019.4
2020.3
2020.3.17f1
2021.1
2021.2
2022.1
Issue ID
1367548
Regression
No
[Text] Unrecognizable character appears as invisible space
How to reproduce:
1. Open the user's attached project "1367548.zip"
2. Load the "SampleScene" Scene
3. In the Hierarchy view go to Canvas > Text GameObject
4. In the Inspector view find a Text component
5. Copy "đź –" characters to Text field in Text component
6. Observe these characters
Expected result: Unrecognizable character is visible
Actual result: Unrecognizable character appears as invisible space
Reproducible with: 2019.4.31f1, 2020.3.19f1, 2021.1.23f1, 2021.2.0b14, 2022.1.0a11
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 (2022.1.X):
Issue is being tracked as a larger feature fix.