Search Issue Tracker
Duplicate
Votes
4
Found in
2018.2.0a3
2018.2.2f1
Issue ID
1068202
Regression
Yes
Some non-latin characters do not appear when typing them into the Input Field
Some of the characters that are affected:
Ą, ą, Č, č, Ę, ę, Ė, ė, Й, К, Е, Н, Г, З, В, А, П, О, Л, Д, Ж, М, И, Б
To reproduce:
1. Open the user's project
2. Enter Play Mode
3. Try typing aforementioned characters (You have to type them yourself, copying them works properly)
Expected result: Character appears in the Input Field
Actual result: Character does not appear in the Input Field
Reproducible with - 2018.2.0a3 ,2018.2.3f1, 2018.3.0a8
Not reproducible with - 2017.4.9f1 ,2018.1.9f1 ,2018.2.0a2
Comments (2)
-
vlob
Aug 29, 2018 00:39
reproducible with 2018.2.5f1
-
blurry73
Aug 08, 2018 02:37
Some Korean characters also do not appear either, and I wish it will be fixed soon.
for example, '가', '바', '서', and there are many more.
I highly suspect that it is related to Font.HasCharacter()
I tested it with 2 version, 2017.2.0f3 and 2018.2.0f2 and
Font.HasCharacter() returns false for those characters with 2018.2.0f,
while it returns true with 2017.2.0f3
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
This is a duplicate of issue #1067159