Hide Forgot
Created attachment 361820 [details] Correct behaviour of 0BC1 and 0BC2 (i.e. without "abvm"). Description of problem: glyphs 0BC1 and OBC2 should not have Anchor Point class as "abvm". Version-Release number of selected component (if applicable): lohit-tamil-fonts-2.4.3-1.fc12.noarch How reproducible: always Steps to Reproduce: 1. Open gedit 2. Input "U+0BB8" + "U+0BC1" 3. Input "U+0BB8" + "U+0BC2" Actual results: 0BB8 + 0BC1 ==> ஸு 0BB8 + 0BC2 ==> ஸூ Expected results: see attachment Additional info: 1) As per http://unicode.org/charts/PDF/U0B80.pdf, OBC1 == TAMIL VOWEL SIGN U OBC2 == TAMIL VOWEL SIGN UU 2) Declaring 0BC1 and OBC2 as "abvm" causes syllable formation "above" the base-glyph (which is wrong behaviour).
Created attachment 361822 [details] ttf file handling correct behaviour of 0BC1 & 0BC2 based syllables
hi felix, can you confirm this thing?
From Comment #1 With the attached font file now it is looking fine and perfect. Eg. the below combination are looking fine: 0BB8 + 0BC1 ==> ஸு 0BB8 + 0BC2 ==> ஸூ Thanks
felix thanks, sandeep can you put submit patch here?
Created attachment 361905 [details] patch handling correct behaviour of 0BC1 and 0BC2 based syllables
build lohit-tamil-fonts-2_4_4-1_fc12 will be available in wed. rawhide
From Comment #6, Correct behaviour of 0BC1 and 0BC2 based syllables can now be obtained from build lohit-tamil-fonts-2_4_4-1_fc12 (available in Rawhide). Hence, closing this bug.
*** Bug 501422 has been marked as a duplicate of this bug. ***
*** Bug 501424 has been marked as a duplicate of this bug. ***