Red Hat Bugzilla – Bug 202161
[ml_IN] Issue with (U+0d30) and (U+0d31)
Last modified: 2016-07-31 21:30:49 EDT
Description of problem:
In the present Malayalam font, for the special combination of :
Any consonant + (U + 0d4d) + (U+0d30) = we get a new glyph with a symbol on the
right side of the consonant, which actually must be on the left side. ie, the
symbol should be before the consonant used.
Also, in the actual malayalam script, for this particular combination,
we have to use (U+0d31) instead of (U+0d30)
ie, we must get the above mentioned glyph when we use:
Any consonant + (U + 0d4d) + (U+0d31). Due to some unknown reasons or ignorance
there are some using (U+0d30) in the community. But I request to change this to
(U+0d31) which is the actual one and hence we shall not follow the same mistake
like others. If at all any questions from community, we can prove this by siting
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open kedit
2. Type any consonant
3. Type (U+0d4d)
4. Type (U+0d30) (according to our present font)
On doing the above steps, we get a new glyph with a symbol after the consonant
but the symbol should have been before the consonant
Ani, the first issue ie, "Any consonant + U+0d4d + U+0d30" has already been
fixed in the latest release of Pango ie, pango-1.14. Please refer the following:
And, regarding the second issue ie the combination "Cons + U+0d4d + U+0d30" has
to be replaced with this combination "Cons + U+0d4d + U+0d31", I am enclosing
the following 2 patches:
1. Pango patch
2. Font patch
Created attachment 134013 [details]
Pango patch attached
Patch about the conjuctions of "Con + 0d4d + 0d31" instead of "Con + 0d4d +
Created attachment 134014 [details]
Font Patch attached
Lizhang, Can you please test the above patches ?
Thanks in advance.
I filed a new bug to Pango, and I wrote a patch for this bug.
The bug is:
I tested it, and this patch of the font file is OK.
In 'Steps to reproduce', its said
'1. Open *kedit*'
*kedit* does not use Pango. Thus Pango patch may not work for kedit or any KDE/QT
application. Lizhang, can you please confirm this.
IMHO the bug needs different fix for QT if implemented within the rendering
A Font patch should work on both the engines. :)
yes, kedit uses qt, doesn't use pango.
But I used a demo of pango to test it, the bug about 0x0d31 is existing, so I
wrote a patch for it.
built in fonts-indic-2.0.1-1
Before Darshan leaving , we had discussion on this and had decided to go with
the correct combination instead of using the wrong one existing in the community.
Hence, any consonant + (U+0d4d) + (0d31) must give a glyph with a symbol on the
left side of the consonant and
Any consonant + (U+0d4d) + (U+0d30) must be just the key sequence .
But what happens in the current font is,
-any consonant + (U+0d4d) + (0d31) gives the output as according to the key
-Any consonant + (U+0d4d) + (U+0d30) gives the output wrong and not even in the
key sequence, there exist a rendering issue with this. ie, its printing in the
order (U+0d30),(U+0d4d) and any consonant which is absolutely wrong
If at all we want to use what is existing in the community, then we can have the
any consonant + (U+0d4d) + (0d31) must give a glyph with a symbol on the
left side of the consonant and
Any consonant + (U+0d4d) + (U+0d30) when used this with (U+200d) can result the
This is what I suggest and if at all any question from community can ba handled.
Which group (Pri A, B, or C) does this bug belong to??
It is Priority A bug. It has been fixed by the patches submitted on bug
#208198, cloned as #209095.
Created attachment 153612 [details]
Bug is verified with following package: