Conversation
Not sure when original hinting was done, but it is not a good match for the glyphs. Removing hinting results in inconsistent stroke widths, but FontForge's autohinting results in inconsistent vertical position which looks worse
No hinting still showed issues, particularly 'm'. Trying FontForge to see how it works in practice.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gftools uses fontmake, which uses ttfautohint by default to autohint .ufo sources when building .ttf files. Unfortunately, that hinting has some issues with ClearType at small sizes and some things like the uneven feet of
mshowing up even at larger sizes. Removing hinting results in less crisp appearance at small sizes but a nicer look overall. See #11 for some examples.While experimenting with hinting and the build process, some differences were found between FontForge's output of .ufo and .ttf formats and those of sfdlib and gftools, respectively. An issue in sfdlib causes points outside a glyph's bounds to be clipped, resulting in #12. FontForge's direct .ttf output fails many fontbakery tests, but its .ufo output doesn't have sfdlib's clipped glyphs and with a little manual cleanup passes fontbakery when built with gftools.
The updates in this PR change the build process from:
to:
fixes #11
fixes #12