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 132591 - blwm marks are not anchored correctly.
blwm marks are not anchored correctly.
Status: RESOLVED FIXED
Product: pango
Classification: Platform
Component: indic
1.2.x
Other Linux
: Normal normal
: ---
Assigned To: Pango Indic
Pango Indic
: 132584 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-01-26 18:59 UTC by blade_x123
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2

Attachments
This is the font file needed to reproduce the above bug. (125.73 KB, application/octet-stream)
2004-01-26 19:01 UTC, blade_x123 		Details
Test file (utf8 text) needed to reproduce above bug. (48 bytes, text/plain)
2004-01-26 19:02 UTC, blade_x123 		Details

Description blade_x123 2004-01-26 18:59:01 UTC 
Here is an image of how the blwm mark needs to be anchored
http://www.ece.uic.edu/~msripada/delme/bug2-correct.png
but this is how it is getting rendered (see the second ligature
due to it's length it seems to be getting stuck somewhere inside the
ligature)
http://www.ece.uic.edu/~msripada/delme/bug2-wrong.png
Attached to this bug is the actual font that is causing the problem
and also a test file.
Comment 1 blade_x123 2004-01-26 19:01:07 UTC 
Created attachment 23777 [details]
This is the font file needed to reproduce the above bug.
Comment 2 blade_x123 2004-01-26 19:02:00 UTC 
Created attachment 23778 [details]
Test file (utf8 text) needed to reproduce above bug.
Comment 3 Owen Taylor 2004-02-21 14:53:19 UTC 
Sat Feb 21 09:49:23 2004  Owen Taylor  <otaylor@redhat.com>
 
        * pango/opentype/pango-ot-ruleset.c (pango_ot_ruleset_shape):
        Sign convention for y offsets is opposite between
        PangoGlyphString and FT code. (#132591)
Comment 4 Owen Taylor 2004-02-21 16:04:15 UTC 
*** Bug 132584 has been marked as a duplicate of this bug. ***