On Sun, May 26, 2013 at 10:54 AM, Dar Scott <d...@swcp.com> wrote: > UTF8 is one of the "languages" of uniEncode and uniDecode functions. > Maybe you can convert to and from UTF8 as you need. Or pull unicode out > of the field and convert that. > > Character 213 is the first of a two byte sequence in UTF8, so a bubble-gum > and tinfoil solution for that lone character would be to force a valid byte > behind it and then remove it when you need. This a bit ugly (I am hesitant > to mention it) but it might have some advantages in your application. >
I'm trying to figure out where they're even coming from! The 213 wasn't utf, but either a mac curlyquote or section symbol (ยง). I don't *think* that two byte codes should be coming out of a normal mac set to english . . . -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
