Red Hat Bugzilla – Bug 247420
[as_IN] Additional special character rendering
Last modified: 2013-04-12 15:13:42 EDT
+++ This bug was initially created as a clone of Bug #247233 +++
Description of problem:
As a part of request from the community, I am including the Unicode character
U+09FA in the Inscript and Phonetic layouts for Assamese. But the rendering of
the character is wrong. The character appears above,to the left of the
consonant/vowel which follows it. At present, it is appearing in the same line
as the character that follows it. Also, it is not a consonant that combines or a
vowel mark that affects the pronunciation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Provided the fonts-bengali are installed, please type the character in raw code.
2. The character should appear to have been typed above left relative to the
next vowel/consonant being typed. Should not depend on what follows it and the
movement to the upper left shouldn't happen after the consonant/vowel that
follows is being typed.
The character is appearing in line with other characters.
The character should appear above the line with other characters.
-- Additional comment from email@example.com on 2007-07-06 02:52 EST --
Created an attachment (id=158643)
Incorrect rendering while typing
-- Additional comment from firstname.lastname@example.org on 2007-07-06 02:58 EST --
Created an attachment (id=158644)
Please note that though the character appears to combine with the consonant, it
is actually not combining. Further more, though the character appears to the
above left of the consonant that follows it, while typing it alone, it should
appear like when you type superscripts, without change in font size.
can i have some update on this matter ? it has been 6 months...
Fixed in fedora, needs to be built for rhel
Fixed in fonts-bengali-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.