After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 516947 - [te] consonant ending (halanth) of conjunct of two or more consonants in telugu is not rendered correctly
[te] consonant ending (halanth) of conjunct of two or more consonants in telu...
Status: RESOLVED FIXED
Product: pango
Classification: Platform
Component: indic
1.16.x
Other Linux
: Normal normal
: ---
Assigned To: Pango Indic
pango-maint
Depends on:
Blocks:
 
 
Reported: 2008-02-17 04:41 UTC by arjuna rao chavala
Modified: 2009-01-25 16:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
Picture illustrating the rendering problem (17.47 KB, image/png)
2008-02-17 04:52 UTC, arjuna rao chavala
Details

Description arjuna rao chavala 2008-02-17 04:41:06 UTC
+++ This bug was initially created as a clone of Bug #516883 +++

Please describe the problem:
Pango when rendering consonant ending of conjuct of two or more consonants should result in a character with removal of tick like mark on the base glyph if it exists and placing of the  u+0c4d on top of the  base glyph. Instead the halanth glyph is being placed after the base glyph. This becomes important when english words are transcribed in telugu which is primarily a vowel ending language
This is also not  done properly by Qt as used in Kword.

Steps to reproduce:
1. Open gedit, select a way of entering telugu characters
2.  enter ka and halanth (u+0c15 u+0c4d soacebar) and how the rendering for single consonant is proper.
3. Enter telugu codes corresponding to ka,halanth to join the next consonant,consonant sa, halanth  to type the last syllable of english word firefox.
 u+0c15 u+0c4d u+0c38 u+0c4d

3. Observe the rendered output where the tick like mark is retained and the halanth comes after the main glyph in stead of in the place of tick like mark.





Actual results:
The tick like mark is retained and the halanth comes after the main glyph

Expected results:
halanth should appear over the base character glyph in place of tick mark if it exists in the base character glyph

Does this happen every time?
Yes

Other information:
This impacts the entire telugu localization efforts, as the resulting characters in the present rendering are incorrect
Comment 1 arjuna rao chavala 2008-02-17 04:52:11 UTC
Created attachment 105415 [details]
Picture illustrating the rendering problem

The second glyph needs to be corrected. The logic that could help
is consonant +halanth+ consonant+halanth+space then the tick mark if it exists should be replaced with halanth for base glyph, else place the halanth glyph on top of the base character
Comment 2 arjuna rao chavala 2008-12-14 11:48:08 UTC
Further investigation revealed that this behavior was not found for Hindi (Devanagari) and Kannada languages.  Changing the telugu font from Lohit Telugu (Fedora default)  to Pothana2000  cleared this problem  in  Ubuntu with Gnome Version 2.22.1-0 .

 Hence this is not a bug in pango,  but a bug in Lohit telugu font.  This bug will be filed in fedora/redhat for resolution
Comment 3 Padmanabhan V. K. 2009-01-25 16:23:52 UTC
The resolution should rather be "NOTGNOME" instead of "FIXED." The bug is in Fedora's telugu font.