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 347073 - Allow empty GPOS table
Allow empty GPOS table
Status: RESOLVED FIXED
Product: pango
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: pango-maint
pango-maint
Depends on:
Blocks:
 
 
Reported: 2006-07-10 04:13 UTC by Behdad Esfahbod
Modified: 2006-07-25 01:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Behdad Esfahbod 2006-07-10 04:13:00 UTC 
Copying from https://bugs.freedesktop.org/show_bug.cgi?id=7455

FontForge creates this empty table instead of just not including the table 
because of Windows: IIRC it requires the GPOS table because it wouldn't read 
the GSUB table if it wasn't in the font.

Pango doesn't like the empty table and gives a warning every time. Note though 
that the empty table is not an error, it can be empty.
Comment 1 Ben Laenen 2006-07-10 12:15:52 UTC 
The place where I got this information was from the FontForge devel list (see http://sourceforge.net/mailarchive/message.php?msg_id=15495969 )

I can't find any reference to empty GPOS tables at http://www.microsoft.com/typography/otspec/gpos.htm but since George Williams stated in the link above that the MS validator says the GPOS table is valid, I'd say there is nothing wrong with an empty GPOS table.
Comment 2 drago01 2006-07-18 14:27:58 UTC 
can this message patched out of pango? 
(the table is ok; so there is no need to warn about it)
Comment 3 Behdad Esfahbod 2006-07-25 01:05:45 UTC 
2006-07-24  Behdad Esfahbod  <behdad@gnome.org>

        Bug 347073 – Allow empty GPOS table

        * pango/opentype/harfbuzz-open.c (_HB_OPEN_Load_ScriptList): Don't
        err on empty GPOS/GSUB tables.