Dear Sir,
I have observed that the Noto Sans Chakma font does not well rendering Some Chakma Character according to rule of Indic Shaping Property of U+11134. Now Windows 10 OS well rendering with RibengUni.ttf. Also well working all apps under this OS. But Firefox and Chrome not work with both font (RibengUni & Noto Sans Chakma). I think there is two issues here one is Font and other is Browser (Chrome & Firefox). So please take a look where is error & why occurs showing such rendering on Chrome and Firefox?
Title
Noto Sans Chakma font not well rendering Ekaara E (U+1112C) with Maayyaa (U+11134) with Virama (U+11133)
Font
Noto Sans Chakma.ttf
Where the font came from, and when
Site: https://www.google.com/get/noto/#sans-cakm
Date: 2017-10-24
Font Version: 2.000;GOOG;noto-source:20170915;90ef993387c0;ttfautohint (v 1.7)
OS name and version
Noto Sans Chakma.ttf
Application name and version
Google Chrome; Version 67.0.3396.99 (Official Build) (64-bit)
Mozila Firefox; 61.0.1 (64-bit)
Observed results:
๐๐ญ๐ช ๐๐ง ๐ฃ๐ฌ๐๐จ๐๐จ๐ข๐ณ๐ ๐๐จ๐๐ด๐ณ๐ ๐ฌ ๐๐๐ง๐๐ด ๐๐ฎ๐๐ด ๐๐๐ด๐
๐๐ ๐๐จ๐๐ด๐ณ๐ฆ๐ฎ ๐ฆ๐ง๐ข๐ง๐๐ด ๐๐จ๐๐ณ๐ ๐ด๐ฌ ๐๐ง๐๐ด๐๐ณ๐ ๐ง ๐ฆ๐ง๐ข๐ง๐๐ด ๐๐ง๐๐ด๐
๐ ๐๐๐ ๐ด ๐๐จ ๐๐
๐๐ฉ
๐
๐๐๐ ๐ด ๐๐ช ๐๐
๐๐ซ
๐ ๐๐๐ ๐ด ๐๐ฌ ๐๐
๐๐ฌ๐ฌ๐
๐๐ณ๐ฃ๐ฎ๐ข๐จ๐ ๐ฅ๐๐ง๐ข๐ด ๐๐๐ฃ๐๐ฌ๐๐ง๐๐ด ๐๐ฌ๐ญ๐
๐๐ ๐๐ด ๐
๐๐ด๐ง๐ข๐ด ๐๐๐ฌ๐ข๐จ๐๐๐ด
Character data
Unicode codepoints:
U+01111F U+01112D U+01112A U+0020 U+01111F U+011127 U+0020 U+011123 U+01112C U+01110A U+011128 U+01111A U+011128 U+011122 U+011133 U+011120 U+0020 U+011107 U+011128 U+011116 U+011134 U+011133 U+011120 U+01112C U+0020 U+011106 U+011118 U+011127 U+011107 U+011134 U+0020 U+011107 U+01112E U+01110C U+011134 U+0020 U+01111B U+01110B U+011134 U+011141 U+000A U+011106 U+011104 U+0020 U+011116 U+011128 U+01111A U+011134 U+011133 U+011126 U+01112E U+0020 U+011126 U+011127 U+011122 U+011127 U+011107 U+011134 U+0020 U+011107 U+011128 U+011116 U+011133 U+011120 U+011134 U+01112C U+0020 U+011103 U+011127 U+01110C U+011134 U+011118 U+011133 U+011120 U+011127 U+0020 U+011126 U+011127 U+011122 U+011127 U+011107 U+011134 U+0020 U+011107 U+011127 U+01111A U+011134 U+011102 U+000A U+011104 U+0020 U+011103 U+01110E U+011120 U+011134 U+0009 U+011103 U+011128 U+0020 U+011103 U+011145 U+0020 U+011103 U+011129 U+000A U+011105 U+0020 U+011103 U+01110E U+011120 U+011134 U+0020 U+011103 U+01112A U+0020 U+011103 U+011145 U+0020 U+011103 U+01112B U+000A U+011106 U+0020 U+011103 U+01110E U+011120 U+011134 U+0020 U+011103 U+01112C U+0020 U+011103 U+011145 U+0020 U+011103 U+01112C U+01112C U+011141 U+000A U+01111B U+011133 U+011123 U+01112E U+011122 U+011128 U+011113 U+0020 U+011125 U+011109 U+011127 U+011122 U+011134 U+0020 U+01111D U+011101 U+011123 U+011118 U+01112C U+01110E U+011127 U+011116 U+011134 U+0020 U+01111A U+01112C U+01112D U+011141 U+0020 U+011104 U+011120 U+01111A U+011134 U+0020 U+011105 U+011116 U+011134 U+011127 U+011122 U+011134 U+0020 U+011103 U+01111F U+01112C U+011122 U+011128 U+011107 U+011116 U+011134
Screenshot
Observed Result:
On Firefox browser with Noto Sans Chakma font:
On Facebook with Firefox browser with Noso Sans Chakma font:
On NotePad in Windows 10 with Noto Sans Chakma font:
Expected Result:
On NotePad in Windows10 with RibengUni font:
Note that, This was possible according to the rule of Indic Shaping Property for U+11134 as below:
https://www.unicode.org/L2/L2016/16303-chakma-maayyaa-chg.pdf