Re: [ft-devel] Experimental: v38 interpreter with minimal backwards compatibility mode and linear advance widths

[Nikolaus Waxweiler]

> >   #ifdef TT_CONFIG_OPTION_SUBPIXEL_HINTING
> >       TT_Driver  driver = (TT_Driver)FT_FACE_DRIVER( face );
> >   #endif
> > +    TT_Driver  driver = (TT_Driver)FT_FACE_DRIVER( face );
>
> What's this?  If the #ifdef is true, you declare and set `driver'
> twice...

Waah, wait, this patch is still a proof of concept, nothing for merging. 
It is incompatible with TT_CONFIG_OPTION_SUBPIXEL_HINTING. I often 
copied stuff from inside the ifdef. Just pretend the 
TT_CONFIG_OPTION_SUBPIXEL_HINTING blocks aren't there.

The idea is that my code, basically a stripped down version of 
Infinality's code, replaces the contents of 
TT_CONFIG_OPTION_SUBPIXEL_HINTING entirely and the define goes away. 
What will happen of course depends on what you think of the idea ;)

> I suggest that we allow advance width changes in native ClearType
> hinting mode, being `better' than MS :-) Applications like web
> browsers can still override this by using the unchanged advance
> widths.

Hm, you mean stop movement in backwards compatibility mode but allow 
when in "native ClearType" mode? A problem I found was with 
"classically" hinted fonts like Arial that space all over the place 
unless you stop changes to the advance widths.