Counting Devanagari Aksharas

[Anshuman Pandey via Unicode]

> On Apr 20, 2017, at 8:19 PM, Richard Wordingham via Unicode <unicode at unicode.org> wrote:
> 
> On Thu, 20 Apr 2017 14:14:00 -0700
> Manish Goregaokar via Unicode <unicode at unicode.org> wrote:
> 
>> On Thu, Apr 20, 2017 at 12:14 PM, Richard Wordingham via Unicode
>> <unicode at unicode.org> wrote:
> 
>>> On Thu, 20 Apr 2017 11:17:05 -0700
>>> Manish Goregaokar via Unicode <unicode at unicode.org> wrote:
> 
>>>> I'm of the opinion that Unicode should start considering devanagari
>>>> (and possibly other indic) consonant clusters as single extended
>>>> grapheme clusters.
> 
>>> You won't like it if cursor movement granularity is reduced to one
>>> extended grapheme cluster.  I'm grateful that Emacs allows me to
> 
>> I mean, we do the same for Hangul.
> 
> Hangul is generally a maximum of three characters, which is about the
> border of tolerance. I find it irritating to have to completely retype
> Thai grapheme clusters of consonant, vowel and tone mark.  There were
> loud protests from the Thais when preposed vowels were added to the
> Thai grapheme cluster and implementations then responded, and Unicode
> quickly removed them. Now imagine you're typing Vedic Sanskrit, with its
> clusters and pitch indicators.

I tried typing Vedic Sanskrit, and it seems to work:

http://pandey.pythonanywhere.com/devsyll

Haven't tried the orthographic oddity of the Nepali case in question. Above my pay grade.

If you access the above link on an iOS device you'll see tofu and missing characters. Apple's Devanagari font needs to be fixed.

- AP

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/unicode/attachments/20170421/c25de933/attachment.html>