Bug 501420 - [ta_IN][GPOS]" U+0BB[8-9] U+0BC1" have error results.
Summary: [ta_IN][GPOS]" U+0BB[8-9] U+0BC1" have error results.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pango
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-19 03:25 UTC by XinSun
Modified: 2009-05-19 03:37 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-19 03:37:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
0BB8-0BC1.jpg (875 bytes, image/jpeg)
2009-05-19 03:25 UTC, XinSun
no flags Details
0BB9-0BC1.jpg (1004 bytes, image/jpeg)
2009-05-19 03:26 UTC, XinSun
no flags Details
0B9C-0BC1.jpg (950 bytes, image/jpeg)
2009-05-19 03:29 UTC, XinSun
no flags Details

Description XinSun 2009-05-19 03:25:54 UTC
Created attachment 344550 [details]
0BB8-0BC1.jpg

Description of problem:
When inputing "U+0BB8 U+0BC" or "U+0BB9 U+0BC" in gedit, the results were wrong.

Version-Release number of selected component (if applicable):
pangomm-2.14.1-1.fc10.x86_64
pango-1.22.3-1.fc10.i386
pango-1.22.3-1.fc10.x86_64
pango-devel-1.22.3-1.fc10.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Select "RAW CODE" in scim-bridge
2.Input "U+0BB8 U+0BC" or "U+0BB9 U+0BC" in gedit.

Actual results:
The result are 

U+0BB8 U+0BC  ஸு

U+0BB9 U+0BC  ஹு

and they are different from the correct images.

Expected results:
Please see the attachment: 0BB8-0BC1.jpg and 0BB9-0BC1.jpg

Comment 1 XinSun 2009-05-19 03:26:39 UTC
Created attachment 344551 [details]
0BB9-0BC1.jpg

Comment 2 XinSun 2009-05-19 03:28:51 UTC
"U+0B9C U+0BC1"  has the same problem.
Actural results:
"U+0B9C U+0BC1" ஜு

Expected results:
Please see the attachment 0B9C-0BC1.jpg

Comment 3 XinSun 2009-05-19 03:29:23 UTC
Created attachment 344552 [details]
0B9C-0BC1.jpg


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