Add ligatures support via libatures
#1671
Draft
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.
Initial glue code to make use of my
libatures
library.This is an alternative to the implementation using
harfbuzz
in #1659.The main advantages of using
libatures
instead ofharfbuzz
are mainly due to the reduced complexity of the library and increased control.This also adds configuration support for ligatures, by providing a new entry in the
options
table ofrenderer.font.load
.By default ligatures are disabled except for the
rvrn
,ccmp
,rlig
and required features.Enabling ligatures by setting the option
ligatures
totrue
will add thecalt
,liga
,clig
anddlig
features.It's possible to fully customize the loaded features by setting
ligatures
to a table which contains the name of the feature as key, and a boolean as value (set tofalse
to disable a "default" feature,true
to enable generic features).For example, setting
ligatures = { ss01 = true, ccmp = false }
will result inss01
to be enabled, as well as all the "default" features, except forccmp
.Closes #66.