Bug 688130

Summary:	URW Palladio Italic font gets dropped when scanned by freetype2 and Scribus
Product:	Fonts	Reporter:	P Linnell <mrdocs>
Component:	free URW	Assignee:	Ralph Giles <ralph.giles>
Status:	RESOLVED FIXED
Severity:	normal	CC:	frob
Priority:	P3
Version:	unspecified
Hardware:	PC
OS:	All
Customer:		Word Size:	---
Bug Depends on:
Bug Blocks:	687297

Description P Linnell 2005-06-07 13:39:26 UTC

Scribus uses some basic sanity checks of the fonts on load to prevent crashes
and PDF issues later on. 

First test is Scribus tries a freetype function  FT_Load_Face when scanning, if
that fails, it's broken. 

Then if that passes, then Scribus tries to determine the exact type (PS, TTF,
OTF, subtypes, format) Then reads font information and fills FT's internal
structures.

Then later another test is made when attempting to use the font:

When the font is used the first time. If FT can not load a glyph with
FT_Load_Glyph, Scribus rejects the whole font. 

This is based on gs 8.11 fonts: ghostscript-fonts-std-8.11.tar.gz 

The URW fonts in True Type do not fail.:
ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/AFPL/GhostPCL/urwfonts-1.41.tar.bz2

Also this is using FT 2.1.9.

Comment 1 P Linnell 2005-06-07 14:46:10 UTC

This is an example error message: Font /usr/X11R6/lib/X11/fonts/URW/p052023l.pfb
has broken glyph 392 (charcode 1035)

Comment 2 Ralph Giles 2005-06-08 07:42:26 UTC

can you check and see if the problem still occurs with valek's new release?

  ftp://ftp.gnome.ru/fonts/urw/release/urw-fonts-1.0.7pre41.tar.bz2

Comment 3 P Linnell 2005-06-09 06:53:29 UTC

Font /home/mrdocs/testing/a010015l.pfb has broken glyph 390 (charcode 1033)
Font /home/mrdocs/testing/a010015l.pfb has broken glyph 328 (charcode 1051)
Font /home/mrdocs/testing/a010015l.pfb is broken and will be discarded
Font /home/mrdocs/testing/n019023l.pfb has broken glyph 320 (charcode 1044)
Font /home/mrdocs/testing/n019023l.pfb is broken and will be discarded
Font /home/mrdocs/testing/n019024l.pfb has broken glyph 460 (charcode 1212)
Font /home/mrdocs/testing/n019024l.pfb has broken glyph 462 (charcode 1214)
Font /home/mrdocs/testing/n019024l.pfb has broken glyph 481 (charcode 1240)
Font /home/mrdocs/testing/n019024l.pfb has broken glyph 483 (charcode 1242)
Font /home/mrdocs/testing/n019024l.pfb is broken and will be discarded
Font /home/mrdocs/testing/c059013l.pfb has broken glyph 356 (charcode 1078)
Font /home/mrdocs/testing/c059013l.pfb has broken glyph 423 (charcode 1175)
Font /home/mrdocs/testing/c059013l.pfb has broken glyph 466 (charcode 1218)
Font /home/mrdocs/testing/c059013l.pfb has broken glyph 486 (charcode 1245)
Font /home/mrdocs/testing/c059013l.pfb is broken and will be discarded

Comment 4 P Linnell 2005-06-09 06:55:37 UTC

The ones is the prior comment were the ones which I found won't load on the
second test Scribus makes when actually trying to use the font. The rest seem to
work fine.

Comment 5 Valek Filippov 2007-05-25 09:10:08 UTC

Peter told me, that this bug isn't reproducible with Suse10.2 fonts (seems to be
more fresh 1.0.7preXX than one used for gs-fonts).
So the new snapshot of gs-fonts is a way to fix it.

Comment 6 p linnell 2007-06-18 13:36:09 UTC

I think this bug now can be closed based on the latest release. I tested it 
quite extensively and no font fails. Recommend closing this.