Re: Courier-Oblique

[Tom Kacvinsky]

Hi David,

Thanks.

I took a look at how FT_Load_Glyph is implemented, and saw that it uses the
autohint module (if one is available for for the current face's driver).

So, I was mistaken several times over this past weekend.  The problems weren't
in T1_Load_Glyph, nor with metrics handling.  The problems were elsewhere, as
you have noted.

Out of curiousity, wouldn't it be better to handle the hint calculations *after*
transform?  The reason why I ask is that in the case of obliquing, the vertical
hints might change position (though not width, etc...).  The horizontals hints
won't suffer from this, though.  Or are hints "attached" to points on the curve,
so that even if the points change position, the hints remain valid?

Regards,

Tom

On Mon, 30 Oct 2000, David Turner wrote:

> Hi Tom,
> 
> > 
> > Oops....  This is not a hinting bug.  In fact, the way T1_Load_Glyph is set 
> > up,
> > hinting is never used.  The bug is somewhere in T1_Load_Glyph, though, and 
> > it
> > can be triggered by turning hinting on and off.
> > 
> > Bart De Lathouwer sent me an email note that the problem might be with the
> > metrics.  Sure enough, when hinting is turned off, T1_Load_Glyph is called 
> > with
> > FT_LOAD_NO_RECURSE, and that is when the font views properly.  But metrics 
> > are
> > handled differently in this case...
> > 
> 
> This is a bug in the auto-hinter. It should be applying the transform
> after processing the glyph outline, but doesn't (silly me !!).
> 
> and in case you wondered, FT_LOAD_NO_RECURSE intentionally disables
> transform processing to let the auto-hinter process un-transformed outlines.
> 
> I'll try to fix this now..
> 
> - David
>