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 528272 - "Error loading GPOS table 5503" when using katakana characters
"Error loading GPOS table 5503" when using katakana characters
Status: RESOLVED FIXED
Product: pango
Classification: Platform
Component: general
1.20.x
Other Linux
: Normal normal
: ---
Assigned To: pango-maint
pango-maint
: 556354 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-15 18:32 UTC by Marco Barisione
Modified: 2008-10-15 10:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
The "guilty" font (454.35 KB, application/octet-stream)
2008-04-15 18:39 UTC, Marco Barisione 		Details

Description Marco Barisione 2008-04-15 18:32:24 UTC 
Using japanese characters from the FreeSans.ttf font in the ttf-freefont package in Debiang I get this warning:
(gucharmap:7207): Pango-WARNING **: Error loading GPOS table 5503

To reproduce it open gucharmap and select Katakana.

I'm using pango 1.20.2 on Debian unstable.
Comment 1 Marco Barisione 2008-04-15 18:39:15 UTC 
Created attachment 109330 [details]
The "guilty" font

The debian package info page is at http://packages.debian.org/sid/ttf-freefont. the font is GPL and copyrighted by FSF.
Comment 2 Michael Gratton 2008-10-14 23:51:46 UTC 
This looks like a dupe of bug #540617.
Comment 3 Behdad Esfahbod 2008-10-15 03:20:25 UTC 
*** Bug 556354 has been marked as a duplicate of this bug. ***
Comment 4 Behdad Esfahbod 2008-10-15 03:45:36 UTC 
Fixed.  Please test.

2008-10-14  Behdad Esfahbod  <behdad@gnome.org>

        Bug 528272 – "Error loading GPOS table 5503" when using katakana
        characters

        * pango/opentype/harfbuzz-gpos.c (Load_Mark2Array): Skip parsing
        null anchor tables.
Comment 5 Michael Gratton 2008-10-15 04:10:44 UTC 
After applying the diff to the 1.22 deb package source and rebuilding/installing it, the warning is gone.

Thanks!