Re: a little unicode help

2012-10-30 Thread Peter Haworth
Interesting. I've had issues with UTF16 and SQLite too so thanks fort the solution. However, according to the SQLite docs, it supports both UTF8 and UTF16 and will convert between them so I wonder why the uniencode/decode calls are necessary. Pete lcSQL Software On Tue,

Re: a little unicode help

2012-10-30 Thread Richmond
On 10/30/2012 05:36 PM, Chris Sheffield wrote: I know several of you out there are unicode "experts". I'm in need of a little help with something. Working on an iPad app. At one point I'm using a native input text field to get the user's name. Until yesterday I was simply retrieving the text p

Re: a little unicode help

2012-10-30 Thread Chris Sheffield
Excellent! That seems to have done the trick. I had thought about trying that at one point, but hadn't quite gotten that far. Thanks again for the help. Chris On Oct 30, 2012, at 10:44 AM, Mark Schonewille wrote: > Hi Chris, > > Are you 1) first retrieving the data from the native text fiel

Re: a little unicode help

2012-10-30 Thread Mark Schonewille
Hi Chris, Are you 1) first retrieving the data from the native text field as unicode, then saving the data to SQLite, then reading it from SQLite and finally setting the text of the LiveCode field or 2) just retrieving the data from the native text field and immediately setting the unicodeText

Re: a little unicode help

2012-10-30 Thread Chris Sheffield
Mark, Here's a selection of my code. It really is quite simple. I first retrieve the text from the native text input control: put mobileControlGet(myInputID,"unicodeText") into tUserName This user name then gets saved to a SQLite database. Then the user name is placed in a LiveCode field using

Re: a little unicode help

2012-10-30 Thread Mark Schonewille
Chris, Post your script to show the encoding. You should encode Russian and English text in exactly the same way. If it works for Russian, then it works for English. If it only disaplays the first character, then there is probable a NULL character somewhere, which indicates double-byte encodin

Re: a little unicode help

2012-10-30 Thread Chris Sheffield
Thanks for the quick reply, Mark. I've tried treating all text as unicode, but the characters from the English keyboard still don't work right. But maybe my problem is in the conversion. So I'm retrieving the unicodeText property of the native text field. Then I'm using the unicodeText property

Re: a little unicode help

2012-10-30 Thread Mark Schonewille
Hi Chris, Just consider all text as unicode. I'm not sure that it is possible to display different types of unicode (Japanese, Hebrew, English, Russian, Thai) next to each other in one field. This used to be impossible, but I hope this was changed in the latest version of LC. -- Best regards

a little unicode help

2012-10-30 Thread Chris Sheffield
I know several of you out there are unicode "experts". I'm in need of a little help with something. Working on an iPad app. At one point I'm using a native input text field to get the user's name. Until yesterday I was simply retrieving the text property of the field and all was working well. B