Converting from unicode to ASCII

Ralph DiMola rdimola at
Tue Sep 22 19:28:33 EDT 2020

How about converting the non ascii characters into to base 64 ascii? This could produce really long filenames. I guess you could truncate if needed. Also the filename would make no sense at all if it was all non ascii.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at

-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at] On Behalf Of J. Landman Gay via use-livecode
Sent: Tuesday, September 22, 2020 6:49 PM
To: LiveCode Mailing List
Cc: J. Landman Gay
Subject: Converting from unicode to ASCII

I have a stack with an index. When a user clicks a line, a handler uses the clicktext to create a file name which is always the clicktext plus the ".livecode" extension. The stack is then downloaded from an AWS server and displayed.

We are now translating some stacks to other languages which require unicode text. AWS recommends not using accented characters in file names, so we need to translate the clicktext into plain ASCII.

Is there a good way to do that without using a lookup table or metadata? The file names doesn't need to make sense syntactically. For example,

    l’Académie française -> lAcademiefrancaise.livecode

...or similar, whatever works. The user will never see the file name.

Jacqueline Landman Gay         |     jacque at
HyperActive Software           |

use-livecode mailing list
use-livecode at
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list