Work around bug in TTFReader subsetting loading #45
Conversation
This file contains 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
the wrong glyph for space
Open
jlarmstrongiv
added a commit
to jlarmstrongiv/fontmin
that referenced
this pull request
Jan 27, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Work around bug in TTFReader subsetting loading the wrong glyph for space. To see this issue you need to pass the option trim: false
This is my work around to fix the second issue mentioned in the following issue when trim is false
#43
It would probably be better to fix it in fonteditor-core, this work around causes it to load more then it needs to.
kekee000/fonteditor-core#7