[Devel] Re: Distiller produced PFA problems

[Tom Kacvinsky]

There was a *simple* fix for the Subrs problem...

Attached is patch that handles the Subrs problem and the FontMatrix
problem.  Let me know if it works for you, or if you see any problems
with it...

I am not sure how to best handle the absence of a FontInfo dictionary.
There are some bits and pieces in the FontInfo dictionary that seem to
be necessary in order for the Type 1 driver to work.  The question is
this: if there is no FontInfo dictionary in the font, should we add
default values?  What should these defaults be?  If we don't add
defaults, perhaps we ought to make the return value alongs the lines
of FT_Error_Missing_FontInfo and leave it up to the user of FreeType
to supply what they think are reasonable values...

Tom

On Thu, 18 Jan 2001, Werner LEMBERG wrote:

> > I'll fix the FontMatrix stuff tomorrow, and look into the Subrs
> > parsing.  The latter is tricky: we have to add logic to the code to
> > take into account the fact the font might reference a non-existant
> > subr (in particular, Subrs 0 - 3).  Which, AFAIK, is OK with Type 1
> > fonts, because Adobe's Type 1 rasterizers trap certain Subrs (Subrs
> > 0 - 3) in C code.  Not that this makes it OK, per se, but
> > conformance with Adobe's Type 1 rasterizers is as good a measuring
> > stick as any.
>
> Hmm, maybe it is easier to add dummy subr structures instead of coding
> a lot of additional guards...
>

t1load.diff
Description: Text document