On 2011-02-19, Werner LEMBERG <[email protected]> wrote: > >> So my suggestion is could FreeType's auto hinter do something like >> this itself - e.g. if when working out all that clever latin blue >> zone stuff, could it realise that actually it's making the font >> smaller and a better result could be obtained by increasing the >> requested pixel height and hinting at that height instead? Or make >> the hinter round up to the next line rather than round down, on the >> basis that rounding up is likely to result in more readable text? > > This is probably dependent on the font. For example, I've just run > ftdiff on pala.ttf, and the autohint's vertical size of glyphs is > basically always the same as with the unhinted glyphs. Do you have > this `problem' all the time, regardless of the selected font? >
aflatin2.c take account the 'drift' accumulated over edge alignment. I guess the bluezone scaling could use the 'drift' too in order to minimize the problem, in af_latin2_metrics_scale_dim(). _______________________________________________ Freetype mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype
