Skip to content

fontlabapp.features.identity_tools.feature_explorer.ligature_finder

ligature_finder

Find underscore-named glyphs and existing input glyphs. Name-derived recipes do not imply outline components.

What it does: Run with a font active. All original controls use the shared fly panel lifecycle. Feature data is font-wide; reopen after switching fonts or changing source.

How it works: Split underscore names into input recipes and check that every input glyph exists and has a safe name. Produce liga text only for usable recipes.

Why this design: An underscore name suggests a ligature recipe but does not prove component structure or existing shaping behaviour.

How to use: Run Features > Ligature Finder. Filter the rows, inspect missing inputs and copy the usable rules for review. Add and compile them separately if they suit the font.

Benefit: Find naming-based ligature candidates without silently adding substitutions or modifying outlines.

Classes

Complete member index

Every captured member retains its own identity. Identical captured declaration text is linked once; this does not establish native inheritance or interchangeable objects.

Member Kind Signature Summary
ACTION attribute
FeaturesDialog attribute (shared captured text)
KEY attribute
QtCore attribute (shared captured text)
QtGui attribute (shared captured text)
SUBTITLE attribute
TITLE attribute
fontlab attribute (shared captured text)
liga_text function (rows: list[tuple[str, str, str]]) -> str Build liga rules for recipes whose input glyphs all exist.
main function () -> Any Replace this tool through the shared owned-window registry. (shared captured text)
qt attribute (shared captured text)
run function (names: Iterable[str]) -> list[tuple[str, str, str]] Return (ligature, space-separated inputs, status) rows in name order.