Open
Conversation
This new util can analyze an input font and generate a segmenter config for it. Currently very early stages.
Numeric value which controls the performance vs quality tradeoff. Lower values maximize performance, higher values maximize segmentation quality (at the cost of longer analysis times).
This allows font2ift to perform the full IFT encoding process: 1. Auto generate segmenter config. 2. Run segmenter. 3. Compile the font. If a segmentation plan is not supplied to font2ift it will then using the segemnter auto config and closure segmenter to generate one.
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.
This adds a new auto segmenter config module which can be used to automatically produce segmenter configs based on an input font. This in turn allows font2ift to go from input font to output IFT font with zero configuration needed.
If no segmentation plan is provided to font2ift then it will use the auto config module to generate a segmenter config, run the segmenter to produce a segmentation plan, and then finally generate the IFT encoded fonts using the compiler.
The current quality level definitions used by the auto config generator were hand picked which is sufficient as a starting point, however as a follow up I'll need to gather data of cost vs encoding times by quality level across a larger corpus of fonts and use that to make more informed selections for the quality level definitions.