support extension table when collecting anchors#19
Merged
Conversation
* do not write a proof with all glyphs if a passed regular expression has no matches * only try to save if proof pages have actually been generated * add `--headless` option to not automatically open proof PDFs
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.
Anchors are not only found in GPOS lookup types 4, 5, 6, they can also be in lookup type 9, which is a GPOS Extension Table. Supporting this makes the
make_anchor_dictfunction quite long with similar collection principles. A future update could streamline the code there (but at least, all anchors are found now).