- From: Norbert Lindenberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Feb 2021 06:49:58 +0000
- To: public-i18n-archive@w3.org
NorbertLindenberg has just created a new issue for https://github.com/w3c/i18n-drafts: == [questions/qa-indic-graphemes] Discuss Indic syllabic categories == [source] (https://w3c.github.io/i18n-drafts/questions/qa-indic-graphemes.en.html) [en] It would be useful to discuss the three categories that the Unicode property Indic_Syllabic_Category uses for viramas: Virama, Pure_Killer, and Invisible_Stacker. Pure_Killer viramas are always rendered visibly and don’t cause conjunct formation. They generally don’t cause the problems described in this article. (MYANMAR SIGN ASAT appears miscategorized, as it is used in representing the kinzi, a conjunct form.) Invisible_Stacker viramas always cause conjunct formation, and should never be rendered visibly. Breaking between such viramas and subsequent consonants is always wrong – and unfortunately that’s what applying extended grapheme cluster rules does. “Virama” viramas are the confusing ones, which are the focus of this article: They sometimes are rendered visibly in a way that breaking after them would be fine, and sometimes they participate in conjunct formation, so that breaking after them causes problems. Please view or discuss this issue at https://github.com/w3c/i18n-drafts/issues/276 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 February 2021 06:50:00 UTC