Read and write OpenType features - #95
Merged
Merged
Conversation
... because of issues with black formatter: Remove empty class, delete trailing spaces
ollimeier
changed the title
justvanrossum
left a comment
justvanrossum
left a comment
Member
There was a problem hiding this comment.
Thank you so much! That's pretty neat. I left some comments.
Co-authored-by: Just van Rossum <justvanrossum@gmail.com>
…ntra-glyphs into opentype_features
10 tasks
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
2 participants
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.
There is no issue for this PR.
Reading the feature code from a GlyphsApp file and converting it to 'feature text' is pretty straightforward with
glyphsLib.builder.features._to_ufo_features(self.gsFont).