Re: [Devel] [slightly-OT] Non-integer bbox for T1 font?

[Tom Kacvinsky]

Leonard,

How did the font choke FreeType?  I can't get it to choke FT...  My tesing
doesn't match your environment, of course...

Oh, BTW, the way, you are correct, this font was made from a MM font.  That
would explain the "real" number bbox.

Tom

On Mon, 5 Mar 2001, Leonard Rosenthol wrote:

> At 2:56 PM -0500 3/5/01, Tom Kacvinsky wrote:
> >Does the customer's font file(s) (PFM + PFB, or suitcase + outline font) work
> >with ATM?
>
>       I don't have the original font file, just the PDF.
>
>
> >  Or is the Type 1 font in question autogenerated?
>
>       I don't know for certain, but from looking at the PDF it
> appears that it may well be generated by the PDF producer in question.
>
>
> >For instance, on a
> >PC platform, the print drivers could be making (depending on how the driver 
> >is
> >configured) a Type 1 font out of a TT font (resulting in non-integer bboxes),
> >and these non-int bboxes are getting passed through to the PDF file
> >when the PS file is distilled.
>
>       No distillation here, direct PDF generation - HOWEVER it
> appears that a MultiMaster font was involved (/BaseFont is
> /MezzMM-OV-WIMOOB).
>
>
> >If the font is autogenerated, we have no way of really testing it with ATM, 
> >so
> >I am guessing in this case that Acrobat Reader (which uses CoolType, right?)
>
>       All Adobe products use CoolType to render text.  That's the
> Adobe Text/Type engine.
>
>
> >I guess I need to see the PS file (was this made with one
> >of Digital Applications products?) and the original PDF file.
> >
>       You want it you got it.   I'll send it via separate mail to
> avoid sending to list.
>
>
> LDR
>