The 'right' or general way to do this (convert text from one character set to
another) is I think always to go through Unicode (back in HyperCard days I had
an external 'viaUnicode' which did exactly this) - this ensures correct
handling of characters with no mapping.
Since LiveCode has some internal mapping tables for a number of character
sets, it should be perfectly trivial to do it using
uniDecode(uniEncode(t, <source charset), <destination charset))
... but unfortunately RunRev have never fixed the original disastrous
decision to make the second parameter of both functions a "language name"
rather than a character set (which of course is what it really is), and to
make some of these an automatically selected character set, ie "ANSI" or
"English" selects Windows-1252 on Windows, Mac Roman on Mac, I've no idea what
it selects on Linux.
So please beg RunRev (I think the voting mechanism has been removed, only
begging remains to us) to give some attention to
http://quality.runrev.com/show_bug.cgi?id=3674
Ben
_______________________________________________
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
