Character sets in Android, iOS, OS/X, Windows

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Character sets in Android, iOS, OS/X, Windows

Tom Glod via use-livecode
There are character set differences between the different platforms, when entered in an app by the user.  Characters slash "/" for example is one of these.

Has anyone detected the same problem?  What would be the intelligent solution to overcome this?  So when a user is typing "ä" (a with umlaut) from Android device soft keyboard, it will be displayed the same on his/her iPAD screen?  The amount of text typed is not large, 100 or so chars.

Unless there is a new trick since LC V7 (just transferring to V8), the only solution would be device-vise use conversionTable[key,os], and maintain it as differences appear.


Christer Pyyhtiä
MindCrea Ltd
Mobile: +358-400-410216
Skype:  christerp1
[hidden email]


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Character sets in Android, iOS, OS/X, Windows

Tom Glod via use-livecode

> On 30 Sep 2017, at 6:48 pm, Pyyhtiä Christer via use-livecode <[hidden email]> wrote:
>
> There are character set differences between the different platforms, when entered in an app by the user.  Characters slash "/" for example is one of these.
>
> Has anyone detected the same problem?  What would be the intelligent solution to overcome this?  So when a user is typing "ä" (a with umlaut) from Android device soft keyboard, it will be displayed the same on his/her iPAD screen?  The amount of text typed is not large, 100 or so chars.
>
> Unless there is a new trick since LC V7 (just transferring to V8), the only solution would be device-vise use conversionTable[key,os], and maintain it as differences appear

Unicode ä should be the same everywhere. Are you sure you aren’t doing something that is native encoding the text during the transfer from one deice to the other? At any point when you write/read the text to/from a file, socket or database you will need to encode/decode it.

/ should be the same everywhere regardless of encoding so that’s a little odd if you are having issues with that!

Cheers

Monte
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode