[cu2qu.ufo] skip processing empty glyphs to support sparse kerning masters #3956
Conversation
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
…sters This will help with the use case described at googlefonts/fontmake#1158 varLib already treats empty glyphs in non-default 'sparse' masters as non participating in gvar interpolation. But if a designspace contains a UFO with such empty glyphs, cu2qu rejects them because it expects all input glyphs to have the same number of segments.
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 will help with the use case described at googlefonts/fontmake#1158
varLib already treats empty glyphs in non-default 'sparse' masters as non participating in gvar interpolation. But if a designspace contains a UFO with such empty glyphs, cu2qu rejects them because it expects all input glyphs to have the same number of segments.