A word of warning ...
It’s really tempting to switch the post table version to 3.0, which then doesn’t store any glyph names in the font, saving file size especially for web fonts.
But for TrueType-based fonts (also packaged in WOFF, WOFF2), doing this will prevent the macOS autohinting from doing its job. Fuzzy contours and uneven stem weights are the result.
I was reminded of this after wondering why some fonts from a well-known monopolist didn’t look very good in the browser.
2
Comments
The effect is not visible in all sizes (shown is 16 px).
When the glyphs are renamed to their proper names, the screen display improves. Again, differences appear only up to 18 px font size.
'post'
table format 3 under most circumstances, as it can create problems with some printer drivers and PDF documents. The savings in disk space usually does not justify the potential loss in functionality.The main files to modify are these two:
https://github.com/HinTak/Font-Validator/blob/master/OTFontFileVal/val_post.cs
https://github.com/HinTak/Font-Validator/blob/master/GenerateFValData/OurData.xml
The change is simple enough that somebody else can have a go at it