[kernFeatureWriter] always write default kern_ltr lookup if non-empty #200
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
And do not duplicate lookup references for LTR scripts, since the kern_ltr lookup appears before any scripts statements and thus will be automatically registered for all defined languagesystems.
|
@khaledhosny PTAL, thanks |
|
LGTM (based on your description). |
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.
Partly fixes #198
This allows to write kerning pairs between arabic numerals (in the LTR lookup) when no LTR languagesystem is explicitly defined, but only some RTL languagesystems (as in NotoSansArabic).
Also, there's no need to duplicate the lookup references to kern_ltr for LTR scripts and languages, since the kern_ltr lookup appears before any scripts statements and thus will be automatically registered for all defined languagesystems.