Red Hat Bugzilla – Bug 206587
[or_IN] - Some GSUB Conjuncts with Priority -B, are not appearing with its correct shape.
Last modified: 2007-11-30 17:11:43 EST
Description of problem:
Some of the Conjuncts in GSUB category are not appearing with its correct shape
after combine. Those Lists are mentioned in the 1st Comment. All these are
priority B or Normal category.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open gedit
2. Activate SCIM with CTRL+SPACE.
3. Select RAWCODE from the scim-table in Others
4. Type the unicode sequentially as given in the 1st comment but without 'U' and
5. Observe the result.
Shapes, appearing is not correct.
Shape should be correctly appearing.
Please see the 1st Comment for the List of Unicode Combinations of conjuncts,
those are showing incorrectly.
List of Conjuncts :
Unicode Combinations :
U+0B19 U+0B4D U+0B15 U+0B4D U+0B24
U+0B26 U+0B4D U+0B2D
U+0B36 U+0B4D U+0B2B
U+0B36 U+0B4D U+0B1F
U+0B37 U+0B4D U+0B1F U+0B4D U+0B2C
U+0B38 U+0B4D U+0B2E U+0B4D U+0B30 U+0B09
U+0B39 U+0B4D U+0B35
U+0B15 U+0B4D U+0B1D
U+0B15 U+0B4D U+0B20
U+0B15 U+0B4D U+0B27
U+0B15 U+0B4D U+0B32
U+0B24 U+0B4D U+0B25 U+0B4D U+0B30
I tested the Font Test Cases with the latest version of fonts available in the
Rawhide. But Fot some pango issue, its showing wrong!! The patch that has
claimed already been developed for this issue resolution, has still not been
built in pango and available as rpm. So, whenever it will be available, I will
again perform the test and the result will be reflected on this bug as comment.
Version tested :
Tested with the following packages, bug still exist.
pango-1.14.4-3 (test rpm)
U+0B19 U+0B4D U+0B15 U+0B4D U+0B24: Image in the test case is definitely a
different combination. The below-base form shown in image is for 0B1A and not 0B24.
U+0B38 U+0B4D U+0B2E U+0B4D U+0B30 U+0B09 : Code points and their description do
not match with each other.
U+0B24 U+0B4D U+0B25 U+0B4D U+0B30: Wrong image in test case
Confirmed with S Behera that test cases are wrong in these cases. Other
combinations work for me.
What are the fix that goes into this bug?? Could it be linked properly, if there
a problem down the track. It will be easier to revert any changes if necessary.
The font patches submitted on bug #206581, along with pango patches #207456,
cloned as #209096, fix this bug as well.
Some Information to be given regarding comment No. #4. Those are :
U+0B19 U+0B4D U+0B15 U+0B4D U+0B24 -- it is correct combination and the image
given is correct.
U+0B38 U+0B4D U+0B2E U+0B4D U+0B30 U+0B09 -- It has been deleted from the TC as
its not an valid combination!!
U+0B24 U+0B4D U+0B25 U+0B4D U+0B30 - The image is showing correct now!
Created attachment 153690 [details]
all combinations are tested on following version: