Sanskrit entry
Posted: Tue May 03, 2016 10:39 am
Whether this constitutes a bug or not, I just don't know, but it is a potential show-stopper if you
are interested in using Livecode for Sanskrit text entry (which I am).
There are currently 2 methods of entering Sanskrit text using the dominant wiring system; the Devanagari abugida:
1. Full entry: this involves using a "lexicon' of up to 5,000 characters.
2. Halant entry: this involves using about 50 characters and about 50 half-characters, called halants.
Currently my problem is with the latter because the Unicode consortium does NOT provide halants in its system, but
it does, apparently, provide a way to get those half-characters, although how exactly this works "under the hood" is a mystery:
trying this in Livecode 7.1 results in this:
which is quite unacceptable.
Performing the same sort of exercise in Livecode 4.5 (using slightly different code [ set unicodeText to numToChar . . . . ]
does no better:
are interested in using Livecode for Sanskrit text entry (which I am).
There are currently 2 methods of entering Sanskrit text using the dominant wiring system; the Devanagari abugida:
1. Full entry: this involves using a "lexicon' of up to 5,000 characters.
2. Halant entry: this involves using about 50 characters and about 50 half-characters, called halants.
Currently my problem is with the latter because the Unicode consortium does NOT provide halants in its system, but
it does, apparently, provide a way to get those half-characters, although how exactly this works "under the hood" is a mystery:
trying this in Livecode 7.1 results in this:
which is quite unacceptable.
Performing the same sort of exercise in Livecode 4.5 (using slightly different code [ set unicodeText to numToChar . . . . ]
does no better: