Search Issue Tracker
Fixed in 4.5.X
Votes
0
Found in
4.3.2f1
Issue ID
594081
Regression
No
Input.inputString doesn't work properly with unicode characters
This issue has no description.
Comments (1)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Alloc
Jan 15, 2015 13:51
Besides the documentation on this being incorrect if Input.inputString is assumed to accept Unicode this issue is in fact not resolved, it only works on Windows, on MacOS and Linux only ASCII characters are reported.
Also see this Unity answers entry: http://answers.unity3d.com/questions/232610/non-ascii-characters-in-inputinputstring-in-osx.html