Lying in the bath, but telling the truth.

Richmond richmondmathewson at
Wed Jun 15 19:12:30 CEST 2016

Ah: "the tail-end of the dictionary entry in LC 8"

Well all that does is allow me the chance to get in a bi*chy comment 
about the LC 8 dictionary
and 64 bit Linux.

There should be, at the very least a browser widget set to load the 


On 15.06.2016 19:33, Devin Asay wrote:
>> On Jun 15, 2016, at 10:27 AM, Richmond <richmondmathewson at> wrote:
> <snip>
>> So, obviously, I will have to set a "bot" to trawl its way through my code
>> and replace every incidence of *numToChar* to *numToCodePoint*, and
>> replace the surrogate pairs in the upcoming *Grantha* interface
>> with "standard" Unicode addresses. The first of which should (?) be relatively
>> simple if the global search-N-replace behaves itself, the second will be a
>> bother, but nothing insurmountable.
>> Anyway; to cut a short story long, as is my wont: to *set the useUnicode to true*:
>> what is unclear from the Livecode 7.x documentation is if this is now redundant
>> or not.
> It’s no longer needed, as it only ever applied to how numToChar and charToNum worked. Here’s a note from the tail-end of the dictionary entry in LC 8:
> Deprecated:In LiveCode 7.0 the language was changed to handle unicode transparently. This means that language functionality which previously aided unicode text manipulation is no longer required. This property should not be used in new code, as it only affects the behaviour of numToChar and charToNum, which are themselves deprecated.
> Devin Asay
> Office of Digital Humanities
> Brigham Young University
> _______________________________________________
> 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