search

googlefonts / opensans

Open Sans font
Other
228 stars 32 forks source link

Hint matching #5

Closed laerm0 closed 5 years ago

laerm0 commented 6 years ago

@davelab6

@m4rc1e and I were talking about the plans to hint this and we won't be able to get total quality on ttfautohint with its defaults, so hinting it in Glyphs seems like best way; that is to say, export the fonts, have glyphs send them through ttfautohint, and then fix the ones that need fixing in Glyphs.

I am currently ensuring point compatibility between weights (hinting point compatibility is more strict than interpolation point compatibility) so that when we fix the glyphs that need better hinting, we only need to fix the regular weight and the hints will get applied to all masters.

davelab6 commented 6 years ago

plans to hint this

I guess that the plan may have changed since April 28; what are the current plans to hint this, both as VF, and as static fonts?

My guess is that we want to ship new static fonts that are hand hinted with no regressions but that solve the long standing problems with Open Sans, and then have a autohinted VF ready to be released when the VF API is completely solid.

I agree that ttfautohint won't be acceptable; but I am also not sure that GlyphsApp can provide the same hinting as exists in the fonts in the API today - my impression is that GlyphsApp only does ClearType hinting, but the API fonts have ClearType, GreyScale and Black&White.

hinting point compatibility is more strict than interpolation point compatibility

I am curious why! :)

m4rc1e commented 6 years ago

hinting point compatibility is more strict than interpolation point compatibility

I am curious why! :)

In VTT instructions are set to each point. If you change the starting point for each curve, even if its all MM compatible, you've broken the hinting.

davelab6 commented 5 years ago

Closing as the plan ended up being VTT