Hi Jacque, Have you looked at the normalizeText function? I’m not sure that would help, but maybe it’s a start.
But it that doesn’t help, and if nobody ever sees the filenames, why not just loop through the string and delete anything that’s not in ASCII range? Devin > On Sep 22, 2020, at 4:48 PM, J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > 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 | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > > _______________________________________________ > 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 Devin Asay Director Office of Digital Humanities Brigham Young University _______________________________________________ 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
