Re: [ft-devel] patch requested for freetype2/internal header usage (using font_bbox)

[Drew Parsons]

On Wed, 2006-01-25 at 11:19 +1100, Drew Parsons wrote:
> > >  
> > >
> > I guess the simpler way is to use a Type 1 font to display the web page
> > (ttheader will be undefined).
> 
> I fear that won't do.  ps/psout_ft.c splits the logic, using
> psout_ftpstype1.c (and ttf2pt1) if the font is type 1, psout_ftpstype3.c
> if it's type3.  Maybe I'll have to try commenting out the type 1
> codepath?  
> 

I was able to test the new code using type 1 fonts by commenting out the
normal type1 codepath to force handling as "type3".  ttheader was
defined this way, giving output looking like 
/FontBBox [0 -124 1024 916] def

(incidentally, is anyone able to say if these are the sort of correct
numbers I should expect to see in a postscript FontBBox?)

I then manually set the ttheader to 0 to force use of the new code
(using ttface->bbox instead of ttheader).  Happily, the same numbers
come out:
/FontBBox [0 -124 1024 916] def

So I guess that's "job done".  Thanks for the help, David.

I've placed the patch at
https://bugs.freedesktop.org/show_bug.cgi?id=603

I think it's not really appropriate to copy the patch to the
freetype.org list of patches for rogue clients, since there are a couple
of other issues in the modular build (unrelated to freetype internals)
which X.org needs to sort out before it will all work (see
http://lists.x.org/archives/xorg-modular/2006-January/000889.html)
Besides, existing installations of Xprint will still build since the
freetype source was included with the X11 source up till now.

Thanks again for the assistance!

Drew