mySQL and accented chars revisited

Peter Haworth pete at lcsql.com
Wed Nov 4 20:08:26 EST 2015


I agree, it is strange it's not in the textEncode entry, never noticed that.

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>

On Wed, Nov 4, 2015 at 5:06 PM, Kay C Lan <lan.kc.macmail at gmail.com> wrote:

> As Peter says. This statement appears in the textDecode entry in the
> Dictionary but for some strange reason not in the textEncode entry. It says
> it all:
>
> It is highly recommended that any time you interface with things outside
> LiveCode (files, network sockets, processes, etc) that you explicitly
> textEncode any text you send outside LiveCode and textDecode all text
> received into LiveCode. If this doesn't happen, a platform-dependent
> encoding will be used (which normally does not support Unicode text).
>
> As stated this includes simple things like reading a text file into LC and
> includes sending to and receiving from any flavour of database. It also
> includes things like using shell - have been tripped up when using ls and
> other shell file utilities that involve file names with accented chars.
> HTH
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the use-livecode mailing list