Bug 497306 - Some unicode do not shown correctly shape in Kannada(U+0CE2 and U+0CE3)
Summary: Some unicode do not shown correctly shape in Kannada(U+0CE2 and U+0CE3)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pango
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Behdad Esfahbod
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 497309
TreeView+ depends on / blocked
 
Reported: 2009-04-23 10:15 UTC by Yewei Shao
Modified: 2009-04-24 05:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 497309 (view as bug list)
Environment:
Last Closed: 2009-04-24 05:45:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Expect results (118.95 KB, image/png)
2009-04-23 10:17 UTC, Yewei Shao 		no flags Details
The wrong results (63.46 KB, image/png)
2009-04-23 10:18 UTC, Yewei Shao 		no flags Details
View All

Description Yewei Shao 2009-04-23 10:15:25 UTC 
Description of problem:
U+0CE2 and U+0CE3 do not show the correctly shape

Version-Release number of selected component (if applicable):
pango-1.14.9-3.el5

How reproducible:everytime


Steps to Reproduce:
1.Type the unicode, like U+0CE2 and U+0CE3
2.Test with kedit
3.
  
Actual results:


Expected results:


Additional info: The actual results and the expected results will be shown in attachment.
Comment 1 Yewei Shao 2009-04-23 10:17:49 UTC 
Created attachment 340922 [details]
Expect results
Comment 2 Yewei Shao 2009-04-23 10:18:17 UTC 
Created attachment 340923 [details]
The wrong results
Comment 3 Behdad Esfahbod 2009-04-24 05:31:02 UTC 
There are more than a dozen of Indic bugs with what we ship.  Unless a specific bug is a regression, or a fix is requested by a customer, I'm hesitant to fix in current releases.
Comment 4 RHEL Program Management 2009-04-24 05:45:20 UTC 
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.