Re: FT2 doesn't like certain Adobe T1 fonts?

[Tom Kacvinsky]

This is probably a bug in ft2 realted to flex hints (Adobe Garamond uses flex
hints).  I patched this just a couple of days ago.  Please try using the latest
CVS version to see if this fixes your problem.

I do not know about the unexpected POP.  After I fixed the driver, I ran
AGarReg.pfa through ftview (a demo prgram that comes with ft2) and it did not
throw that error.

Which version of Adobe Garamond is your customer using?

Regards,

Tom

On Wed, 11 Oct 2000, Leonard Rosenthol wrote:

> I apologize if this is a FAQ, but I couldn't find anything in on the 
> FT website or in the FT2 sources/docs.
> 
> I have deployed FT2 (b8) as part of a SVG rendering engine (on Mac OS 
> and Windows), and it's been working great for a while now - thanks 
> for everyone associated with FT!
> 
> However, as the renderer supports the use of external fonts, one 
> customer has discovered that when using certain Type 1 fonts from 
> Adobe (AGaramond, for example), bad things happen.
> 
> I've tracked it into the fact that FT2's T1 "driver" thinks the font 
> is invalid, specifically the parser throws an error about an 
> "unexpected POP".
> 
> Anybody know what the story is here - and most importantly, how to fix it?
> 
> 
> Thanks,
> Leonard
>