LC Server UT08 Encode Error
Dar Scott Consulting
dsc at swcp.com
Fri Sep 13 20:29:19 EDT 2019
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 <use-livecode at lists.runrev.com> wrote:
> 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 to compare the string from
> Pages that I pasted to the the string that
> I had cleaned with BBEdit. The only
> differences found was a 000A <control>
> and a few 00A0 (NO-BREAK SPACEs).
> I suspect it is the control character really
> screwing things up. (I don’t know how
> it got into the string.)
> I am not using the accept-charset attribute
> in the <form> statement. If not specified
> it is supposed to use the default which I’m
> guessing is UTF-8. I supposed I could try
> a test with the attribute specified to see if
> it makes any difference.
>> On Sep 13, 2019, at 5:36 PM, Dar Scott Consulting via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 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 an accept-charset attribute in <form>? Maybe fiddling with that will help.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode