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
- 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
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