Closed Bivuti closed 5 years ago
@Bivuti : why is this one incorrect? what is wrong here?
why is this one correct? what is correct here?
are both of them readable by the native users?
This works in Noto Chakma when the order of marks is the other way around (1112D 11134), but that order doesn't even make any sense because that would mean it's considered a Pure Killer (the original Indic Syllabic Property) so no vowel would follow it. The Indic Syllabic Property was then changed to Gemination Mark. That means the lookup that does work in Noto Chakma is backwards. According to the original properties that would have been correct, but since 11134 has changed this lookup needs to be updated. I'll fix it.
@punchcutter The first question answer is Noto Sans Chakma not rendering well of this sequences U+11107 U+11134 U+1112D = 𑄇𑄴ð‘„. So it's incorrect as the people could not spell out it In Chakma.
The second question is RibengUni well rendering of this sequences U+11107 U+11134 U+1112D = 𑄇𑄴ð‘„. So it's correct. People easy spell out this word.
Here is also some special Chakma words that still not well rendering your Noto Sans Chakma font. The comparison text is given as below:
Please also update this one.
Thanks Bivuti
Ok Bivuti, no problem. When you put a screenshot can you please also put the raw text or codepoints? That helps so that anyone can test the issue. For this issue we now have U+11107 U+11134 U+1112D = 𑄇𑄴𑄠U+11107 U+11134 U+11130 = 𑄇𑄴𑄰 Those will be fixed in the next update.
@punchcutter Thanks for your suggestion. Sounds great! I would be happy that to help you about Chakma Language any confusion/complicated words when you will be implementing in modern technology. And also any Chakma font issue.
Cheers Bivuti
Hi, I found that your "Noto Sans Chakma.ttf" font doesn't correct rendering some special Chakma words yet. I attached the rendering compare screenshot for your kind attention.
Please take a look at this issue.
Thanks Bivuti Chakma