Converting from unicode to ASCII
richmondmathewson at gmail.com
Wed Sep 23 02:19:11 EDT 2020
Personally I think deleting everything that is not inwith the ASCII range
is potentially a bit dangerous [suppose ALL the letters
in the title are not inwith the ASCII range], so I would favour using some
sort of lookup table/substitution list. Certainly letters such
as accented 'e' can just be replaced by a 'common or garden e', but,
consider Cyrillic for instance. Of course a lot of this has to
do with what sort of source files you are using [Hmong, anyone?].
Most alphabetic languages have a standardise Latin transliteration standard
and that is best adhered to, so, for instance:
Ричмънд (in Bulgarian Cyrillic), comes across as 'Richmand' [OK, OK, OK,
it's hilarious, but that's what you get when a
transliteration standard is worked out by a committee of people who
couldn't tie their own shoelaces (that's why they sit in
Certainly, however WONKY a Latin transliteration scheme maybe both
phonetically and in general, that should NOT need to
be considered when it comes to file names.
On Wed, Sep 23, 2020 at 6:43 AM Mark Wieder via use-livecode <
use-livecode at lists.runrev.com> wrote:
> On 9/22/20 7:58 PM, J. Landman Gay via use-livecode wrote:
> >> Is this just a temporary filename (not long-term storage)?
> > No, the stacks are uploaded to AWS and remain there, retrieved from the
> > server on request. There are currently hundreds of them with more added
> > frequently. That's why I'm looking for a solution that doesn't involve
> > changing all the file names, because renaming and re-uploading all those
> > files would be way too much work.
> How do the files get retrieved? Is there a database or something similar
> that stores the filenames? You could still use UUID filenames from now
> on and not have to mess with the existing ones.
> Mark Wieder
> ahsoftware at gmail.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
This communication may be unlawfully collected and stored by the Agents
of a large number of governments in secret. The parties to this email do
not consent to the retrieving or storing of this communication and any
related metadata, as well as printing, copying, re-transmitting,
disseminating, or otherwise using it. If you believe you have received
this communication in error, please delete it immediately.
More information about the use-livecode