Yes. A0 looks like the middle of a sequence of UTF-8 bytes for one character.
Hitting that will cause an error.
I wonder why the db complained about CA and 59.
> On Sep 13, 2019, at 4:10 PM, Rick Harrison via use-livecode
> wrote:
>
> Hi Bob and Dar,
>
> Thanks for getting back to me on
Hi Bob and Dar,
Thanks for getting back to me on this.
After going through the LC list archives,
I came across a helpful tool called
"Unicode Checker” that was originally
suggested by Richmond Mathewson.
(Thanks for that by the way.)
There is a nice little utility inside of it that
allowed me
On Thu, Sep 12, 2019 at 1:42 PM Sannyasin Brahmanathaswami via use-livecode
wrote:
> Been working Panos off list.
>
> There is a caveat, jsonImport and jsonExport not only "display" but
> "preserve" the scientific notation as a literal string and math will fail.
>
> Panos says: must use, (and
When you Zap Gremlins, are you removing non-ASCII or converting to ASCII? Maybe
you can do the same thing before saving to the db.
Codes 0xca 0x59 do form an invalid UTF-8 sequence. They are good letters in
both Latin-1 and CP1252, so I'm not getting a hint.
Wild, wild guess... Are you using
Based on the source of the data, I'm going to say it's an encoding issue. I
cannot imagine that pages is embedding non-printing characters that get past
the clipboard.
Bob S
> On Sep 12, 2019, at 18:21 , Rick Harrison via use-livecode
> wrote:
>
> I am having a problem with LC Server
>
Danke Hermann.
I am still planning to use something like this.
I have database with all dutch postcode with housenr's and longitudes
and latitudes. This is now public information ordered some years ago by
a Dutch Federal Judge as the post delivery appealed against this. But it
is not easy to
