You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #193. At first glance, scrcpy is THE application that would finally make touchscreen pocket computers (i.e. smartphones) anything other than annoying toys to slowly mistype on for me. However: The method you use for sending text input from computer to android gadget makes use of ADBs builtin string injection primitives, which seem to be limited to UTF-7. Hence, language use when typing is limited to ASCII, which means it's in practise really only usable for English, not much else. Especially not Swedish, since the letter "å" cannot be worked around in the code by using a combination of a diacritical dead key with "a".
I realize adding support for Unicode input would almost certainly necessitate pushing some kind of injector app onto the Android thingy. Some kind of... fake keyboard app. I know too little of Android to speculate. So you may not want to implement it. It would be great if you did, though.
Moreover, I consider that whoever made the design decision in Android to limit "adb shell input text" to UTF-7 should be crucified. But that's neither here nor there... :-)
The text was updated successfully, but these errors were encountered:
Related to #193. At first glance, scrcpy is THE application that would finally make touchscreen pocket computers (i.e. smartphones) anything other than annoying toys to slowly mistype on for me. However: The method you use for sending text input from computer to android gadget makes use of ADBs builtin string injection primitives, which seem to be limited to UTF-7. Hence, language use when typing is limited to ASCII, which means it's in practise really only usable for English, not much else. Especially not Swedish, since the letter "å" cannot be worked around in the code by using a combination of a diacritical dead key with "a".
I realize adding support for Unicode input would almost certainly necessitate pushing some kind of injector app onto the Android thingy. Some kind of... fake keyboard app. I know too little of Android to speculate. So you may not want to implement it. It would be great if you did, though.
Moreover, I consider that whoever made the design decision in Android to limit "adb shell input text" to UTF-7 should be crucified. But that's neither here nor there... :-)
The text was updated successfully, but these errors were encountered: