Closed davelab6 closed 10 years ago
http://jsbin.com/xoxev/edit reproduces the incorrect rendering that is also seen on blogger, but I do not see the same issue on http://www.idc.iitb.ac.in/~girish/demo/#/16 given the same string...
OK :) http://jsbin.com/viqub/edit reproduces the correct rendering.
Seems Mac Chrome is not always applying the 'liga' OpenType feature, but this can be corrected by specifying it in the CSS, -webkit-font-feature-settings:"liga" 1;
proper shaping should not rely on the
@pauldhunt Noto Sans Devanagari exhibits the same issue, http://jsbin.com/waxaxeka/1/edit
I have reported this to Chrome and they seem to accept the issue is with them.
However, @pauldhunt is correct and my previous comment was incorrect - looking at http://jsbin.com/waxaxeka/3/edit on a Mac Chrome, I see Noto Sans Devanagari appears to be working correctly despite this flaw in Chrome.
I hope Ek Mukta can be updated to render with the same OTL techniques Noto Sans is using.
Okay, looks like https://github.com/girish-dalvi/Ek-Mukta/commit/99f601f2d9147bdc3068ecea2ebba71a4ea36f07 fixed it, please see http://jsbin.com/waxaxeka/3/edit versus http://jsbin.com/waxaxeka/5/edit
A sample blog using Ek Mukta is at http://srichatest1.blogspot.in/
Here is a comparison of Ek Mukta and Noto Sans:
This shows some rendering issues with Chrome on Mac OS X
Dynamic rendering issues for a same word. For example, here is a close up of the first two words highlighted in the red and orange boxes in the above:
This is reported only in Chrome; Firefox works fine.