Red Hat Bugzilla – Bug 239630
[hi_IN] the glyph of 0x0953 in lohit_hi.ttf is wrong.
Last modified: 2013-04-12 15:08:41 EDT
Description of problem:
The glyph of 0x0953 in lohit_hi.ttf is wrong. It is different with the glyph of
0x0953 in Unicode 5.0
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The below wrong image
The below right image
Created attachment 154446 [details]
the wrong glyph of 0x0953 in our font file
Created attachment 154447 [details]
the right glyph of 0x0953 in Unicode 5.0
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This looks worth fixing for 5.2, right?
(In reply to comment #5)
> Rahul: "This one is not a serious issue according to me, since it does not
> hamper any use of the script technically. It would be considered a
> quality of shape preference."
Oops, sorry that was for another bug.
Rahul: "This is a glyph drawing problem."
Not being a major issue,and since its late for 5.2 , this bug should be pushed
Created attachment 296589 [details]
glyph U+0953 (Devanagari Grave Accent) included in the ttf
Created attachment 296594 [details]
Screenshot showing U+0953 placed above U+0915 (Devanagari Letter KA)
Fixed in lohit-fonts-hindi-2.2.0. Need to be built for RHEL.
This bugzilla was reviewed by QE as a non-FasTrack request.
It has since been proposed for FasTrack. The qa_ack has
been reset. QE needs to re-review this bugzilla for FasTrack.
Fixed in fonts-hindi-2.3.1-1.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.