Skip to content

feature: support GSUB 6 and 4 (contextual ligs)#3

Merged
corytodd merged 2 commits into
mainfrom
corytodd/add-contextual-context
Mar 15, 2026
Merged

feature: support GSUB 6 and 4 (contextual ligs)#3
corytodd merged 2 commits into
mainfrom
corytodd/add-contextual-context

Conversation

@corytodd
Copy link
Copy Markdown
Owner

Generate rules for when to replace the sequence with a ligature. This
is based on my understanding of the Fira code approach where a marker
glyph is used to prevent matching in forbidden sequences. Currently,
the sequence may only trigger when surrounded by white space.

Generate rules for when to replace the sequence with a ligature. This
is based on my understanding of the Fira code approach where a marker
glyph is used to prevent matching in forbidden sequences. Currently,
the sequence may only trigger when surrounded by white space.
FontTools warns that the glyphs are not sorted correctly. Not sorting
correctly produces a technically invalid font but the shapers I've used
seem to not mind. There is probably a scenario where a glyph lookup
would fail so let's fix this now.
@corytodd corytodd merged commit 713725c into main Mar 15, 2026
1 check passed
@corytodd corytodd deleted the corytodd/add-contextual-context branch March 15, 2026 18:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant