[Bug 524457] New: [ta_IN] Anchor Point class for 0BC1 and OBC2 should not be "abvm"

[Red Hat Bugzilla]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: [ta_IN]  Anchor Point class for 0BC1 and OBC2 should not be "abvm"

https://bugzilla.redhat.com/show_bug.cgi?id=524457

           Summary: [ta_IN]  Anchor Point class for 0BC1 and OBC2 should
                    not be "abvm"
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Keywords: i18n
          Severity: medium
          Priority: low
         Component: lohit-tamil-fonts
        AssignedTo: psatpute(a)redhat.com
        ReportedBy: sshedmak(a)redhat.com
         QAContact: extras-qa(a)fedoraproject.org
                CC: fedora-fonts-bugs-list(a)redhat.com,
                    psatpute(a)redhat.com, fedora-i18n-bugs(a)redhat.com
    Classification: Fedora
    Target Release: ---


Created an attachment (id=361820)
 --> (https://bugzilla.redhat.com/attachment.cgi?id=361820)
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).

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.