Hello, The BadWindow errors are probably unrelated to the GPOS errors, but I've attached a patch (backported from gnome CVS) that makes pango not give errors on empty GPOS tables.
-- +------------------------------------------------------------------+ | John Wright | Open Source and Linux Organization (OSLO) | | 970-898-3171 | Hewlett-Packard | | [EMAIL PROTECTED] | Fort Collins, CO | +------------------------------------------------------------------+
=== added file 'debian/patches/10_allow_empty_gpos_table.patch' --- debian/patches/10_allow_empty_gpos_table.patch 1970-01-01 00:00:00 +0000 +++ debian/patches/10_allow_empty_gpos_table.patch 2006-08-11 23:42:35 +0000 @@ -0,0 +1,20 @@ +diff -Nur pango-1.12.3.orig/pango/opentype/ftxopen.c pango-1.12.3/pango/opentype/ftxopen.c +--- pango-1.12.3.orig/pango/opentype/ftxopen.c 2006-01-30 15:37:48.000000000 -0700 ++++ pango-1.12.3/pango/opentype/ftxopen.c 2006-08-11 17:33:47.000000000 -0600 +@@ -250,11 +250,16 @@ + (void)FILE_Seek( cur_offset ); + } + ++ /* Empty tables are harmless and generated by fontforge. ++ * See http://bugzilla.gnome.org/show_bug.cgi?id=347073 ++ */ ++/* + if ( sl->ScriptCount == 0 ) + { + error = TTO_Err_Invalid_SubTable; + goto Fail; + } ++*/ + + return TT_Err_Ok; +
