RE: [Devel] Problem with caching and CFF fonts [was: pure CFF fon ts and advanced widths]

[Blinn, Eric W]

I actually hadn't noticed this problem until Tom pointed 
it out... probably because I'd only recently jumped up 
from Beta 8 and newer versions of ftview were not opening 
CFF fonts (until Tom's recent fixes).

I just tried Werner's suggestion, and used the ftview from 
the Beta 8 demos, but linked it against the current library 
snapshot. The lines do advance fine under that scenario. So 
that would seem to isolate the problem to the changes made 
to allow ftview to use the cache module (or else some other 
change to ftview or how it is built).

> ----------
> From:         Werner LEMBERG[SMTP:address@hidden
> Sent:         Tuesday, November 28, 2000 7:07 AM
> To:   address@hidden
> Cc:   address@hidden
> Subject:      Re: [Devel] Problem with caching and CFF fonts [was: pure
> CFF fonts and advanced widths]
> 
> 
> > So, I suspect this is a problem with the caching subsystem of
> > FreeType 2.  As for the font in question (CMEX10Pro.cff), that is a
> > CFF font made by extracting the `CFF ' table from an OpenType/CFF
> > font I made with Adobe's OpenType FDK.  The full-on OpenType font
> > (CMEX10Pro-Regular.otf) views just fine, and the fprintf prints out:
> > 
> >     Render_All: step_y: 138, size->metrics.height: 8576.
> 
> Maybe you can dig out (either from the CVS or from a beta version) an
> older version of ftview for testing which doesn't use the cache
> module.
> 
> 
>     Werner
> 
> _______________________________________________
> Devel mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/devel
>