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
- [Android][iOS][UnityPlayerActivity] Legacy InputField.onEndEdit is not called when ending text edit
- Transform corruption and/or crash on PhysX::CreateCharacterController when spawning physics objects into Prefab stages
- UNITY_EDITOR data is Serialized into AssetBundle when building on the active Build Target
- "TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations..." error when changing the Packages "Cache Location" folder
- CompilationPipeline.assemblyCompilationFinished() hangs unity when reloading domain
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