Red Hat Bugzilla – Bug 206387
[ml_IN] the glyph of the conjuction of 0x0d32 + 0x0d4d + 0x0d32 is wrong.
Last modified: 2015-04-06 23:06:39 EDT
Description of problem:
The glyph of the conjuction of 0x0d32 + 0x0d4d + 0x0d32 is wrong with using
lohit_ml.ttf of fonts-indic-2.0.1-1. But it is right with using Lohit_Malayalam.ttf.
The image of comparing the results is below:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 136222 [details]
The image of comparing
The effect is due to the general below base implementation of 0x0d32 in Pango.
Earlier font had a rule compatible with this implementation. Then it was reported
by LM, Ani, that below base form takes place only when 0x0d32 combines with
itself. In every other case, such below base forms should be formed using 0x0d33.
But it seems that every other system has implemented 0x0d32 as genneral below
base form for all the consonants it combines with. Their is a disput among
about the valid correct character i.e. either 0x0d32 or 0x0d33. This bug can be
fixed in Pango assuming 0x0d33 is the correct below base character. But it needs
information from Ani about the confirmation and a strong community feedback on
Ani, could you get a feedback or some official documents supporting any of the
Give me two days time. By Monday I will let you know the final stand.
The patch on bug #192934 (attachment id=137177) makes the rendering of 0d32 and
0d33 conjuncts identical to each other and special for 0d32+0d4d+0d32 and
*** Bug 207093 has been marked as a duplicate of this bug. ***
Created attachment 153617 [details]