> > Is relocation ever triggered while uncompressing fonts? If yes, is > > the corresponding font correctly read and displayed?
Oh yesss! $ bin/ftview 44 ../hanglg16.pcf.Z pcf_get_metrics: invalid metrics for glyph 2081 pcf_get_metrics: invalid metrics for glyph 2082 pcf_get_metrics: invalid metrics for glyph 2083 pcf_get_metrics: invalid metrics for glyph 2084 pcf_get_metrics: invalid metrics for glyph 2085 pcf_get_metrics: invalid metrics for glyph 2086 pcf_get_metrics: invalid metrics for glyph 2087 pcf_get_metrics: invalid metrics for glyph 2088 pcf_get_metrics: invalid metrics for glyph 2089 pcf_get_metrics: invalid metrics for glyph 2090 pcf_get_metrics: invalid metrics for glyph 2091 pcf_get_metrics: invalid metrics for glyph 2092 pcf_get_metrics: invalid metrics for glyph 2093 pcf_get_metrics: invalid metrics for glyph 2081 pcf_get_metrics: invalid metrics for glyph 2082 pcf_get_metrics: invalid metrics for glyph 2083 pcf_get_metrics: invalid metrics for glyph 2084 pcf_get_metrics: invalid metrics for glyph 2085 pcf_get_metrics: invalid metrics for glyph 2086 pcf_get_metrics: invalid metrics for glyph 2087 pcf_get_metrics: invalid metrics for glyph 2088 pcf_get_metrics: invalid metrics for glyph 2089 pcf_get_metrics: invalid metrics for glyph 2090 pcf_get_metrics: invalid metrics for glyph 2091 pcf_get_metrics: invalid metrics for glyph 2092 pcf_get_metrics: invalid metrics for glyph 2093 $ bin/ftview 44 ../hanglg16.pcf is clean as a whistle!
