Repository navigation
Conversation
- A soft hyphen replaced by its case form was still swapped for an invisible space, as the substituted glyph keeps the soft hyphen's code point - Hide only default ignorables that still show their nominal glyph, as HarfBuzz does - Add tests for hiding a soft hyphen and keeping its case form, with Fira Sans
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.
Observed with real fonts: Fira Sans (already in the test data) and our Akkurat family ship a
caseform of the soft hyphen (uni00AD.case). HarfBuzz shows it in"AB"withcaseon; fontkit swaps it for an invisible space.hb-shape --features=case FiraSans-Regular.ttf "AB"givesA uni00AD.case B)