Unicode is binary??
> Bob S
not unicode per se Dictionary says
*Syntax*
textEncode(*stringToEncode*, encoding)
*Summary*
Converts from text to binary data.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscr
Unicode is binary??
Bob S
> On Oct 14, 2018, at 17:35 , Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> On 10/14/18 8:43 AM, J. Landman Gay via use-livecode wrote:
>> I'd store the text normally, without alteration, in the JSON. TextEncode
>> it when you send it to the database and
> On 16 Oct 2018, at 12:09 am, Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> A "Related" entry under textDecode and textEncode might help.
>
> The problem is when you get to a dictionary entry for those, there is no
> mention "mergJSON".
>
> So not matter how well "mergeJSON" is d
On 10/14/18 5:41 PM, Monte Goulding via use-livecode wrote:
> Well mergJSON is documented to return UTF-8 encoded JSON, however, I agree
> that JSONImport and JSONExport docs are a little ambiguous and should clarify
> that the JSON needs to be textDecoded before calling JSONImport and
> textEnc
> On 15 Oct 2018, at 2:31 pm, Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> First can you clarify if both of these should work.? We see both in
> dictionary...
>
> *Example*
>
> textEncode("A","UTF16")
>
> *put*textEncode(field"output","UTF-8") intotOutput
>
> will the 2nd param
First can you clarify if both of these should work.? We see both in
dictionary...
*Example*
textEncode("A","UTF16")
*put*textEncode(field"output","UTF-8") intotOutput
will the 2nd param work with or without a hyphen?
---
unclarity --simply:
*Syntax*
textEncode(*stringToEncode*, encod
> On 15 Oct 2018, at 11:35 am, Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> Wow, that worked! And I thought that JSON could not be a container for
> "binaryData" as described on the dictionary.
Could you provide some detail where the docs are misleading. It is actually
true that
On 10/14/18 8:43 AM, J. Landman Gay via use-livecode wrote:
> I'd store the text normally, without alteration, in the JSON. TextEncode
> it when you send it to the database and textDecode when you retrieve it
> from the database.
Wow, that worked! And I thought that JSON could not be a container
I'd store the text normally, without alteration, in the JSON. TextEncode
it when you send it to the database and textDecode when you retrieve it
from the database.
On 10/14/18 9:26 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
I need to store unicode in JSON on Mobile; and store that
I need to store unicode in JSON on Mobile; and store that in SQLLite dBase
If you do a "direct" transfer
*put*(char1to35oftQuote)& "..."intosTruncFirstLine
"Yea, jīva is actually Śiva."
# putting sTruncFirstLine into an SQLLite column
# when you get the data out, it becomes
"Ye
10 matches
Mail list logo
