Bug 218905 - [ta_IN] Some conjunct characters not appearing with proper shape
Summary: [ta_IN] Some conjunct characters not appearing with proper shape
Alias: None
Product: Fedora
Classification: Fedora
Component: pango
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact:
Whiteboard: bzcl34nup
Depends On: 217353
Blocks: Indic
TreeView+ depends on / blocked
Reported: 2006-12-08 07:47 UTC by Parag Nemade
Modified: 2009-02-04 07:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-07 01:02:30 UTC
Type: ---

Attachments (Terms of Use)

Description Parag Nemade 2006-12-08 07:47:47 UTC
+++ This bug was initially created as a clone of Bug #217353 +++

Description of problem:
   This is with tamil font problem. Following combinations was found not
rendering properly after fixing font file for bug 217341.
gsub : U+0BB6 U+0BBF 
gpos : U+0BB6 U+0BC0
       U+0BB6 U+0BCD

Version-Release number of selected component (if applicable):
and modified tamil font file attached in bug 217341

How reproducible:

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.
Actual results:
combinations are appearing as split and 2 characters

Expected results:
Combinations should appear as single final character image

Additional info:

-- Additional comment from pnemade@redhat.com on 2006-11-27 07:32 EST --
Created an attachment (id=142164)
This patch solves the reported bug

-- Additional comment from besfahbo@redhat.com on 2006-12-04 13:15 EST --
LingNing, any comments on this?

-- Additional comment from lizhang@redhat.com on 2006-12-04 21:36 EST --
U+0BB6 is existing in Unicode 5, it is consonant. But it is not existing in
IndicOTCharClass of Pango, it is only "_xx", so it need be modified to "_ct".
The patch of parag did this.
And I think there are many characters' class which need be modified because of
updating in Unicode 5 in IndicOTCharClass of Pango.

Comment 1 Liang Zhang 2007-09-28 08:33:36 UTC
The upstream bug:

Comment 2 Bug Zapper 2008-04-03 18:46:27 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 3 Bug Zapper 2008-05-07 01:02:28 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

Comment 4 Padmanabhan V. K. 2009-01-23 17:20:22 UTC
Please reopen this bug. The bleeding edge version of Pango still has U+0BB6's type as _xx instead of _ct:


and http://bugzilla.gnome.org/show_bug.cgi?id=481203 is still open.

Comment 5 Venkatraman Balasubramanian 2009-02-04 07:29:05 UTC
This is a huge disturbance in using my Linux box. This U+0BB6 works great when combined with U+0BC7 etc., in my Mac OSX box. 

Like Padmanabhan stated here, Pango has to be fixed to make Linux be in compliance with Unicode 4.1 and higher. Please re-open this bug.

Note You need to log in before you can comment on or make changes to this bug.