Fix ligatures flag for Recursive font
#60
Merged
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
|
You got a sec to re-run the screenshots and see if the work with the ligatures? We have a number of fonts I just couldn't get them working on #52 and I'd love to have a good example of them working to use to try to fix the others. |
|
@chriscoyier here are screenshots generated with
However, with other fonts listed in #52, ligatures don't seem to work for them (tested with Hasklig and FiraFlott). |
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.
Recursive font seems to support ligatures. On the website it shows that it doesn't. This PR fixes that.
Cheers,