Does an unexpanded ligature look wrong on the page?

No, it renders exactly as intended, since the ligature glyph is a legitimate part of the font. The problem only shows up in the extracted text, where the ligature's own Unicode codepoint isn't the letters it visually represents.

Will a search for a word with "fi" or "fl" in it match text containing the ligature glyph?

Not unless the ligature is expanded back to separate letters first. The ligature codepoint and the two-letter sequence it visually represents are different characters to a plain-text search, even though a human reads them as identical.

Ligature

A single glyph that visually fuses two or more letters (fi, fl), left unexpanded, extracts as an unrecognized symbol instead of separate characters.

definition

A ligature is a single glyph in a font that visually combines two or more letters, commonly fi, fl, or ffi, into one connected shape. It exists for typographic quality, not meaning.

Also called: typographic ligature, fi/fl ligature

in-plain-terms

Typesetting has used ligatures for centuries. Certain letter pairs collide awkwardly when set as separate glyphs, so a ligature glyph redraws them as one connected shape that reads more cleanly. The font still only has one glyph for "fi", not two.

A good text extractor expands a ligature glyph back into its component letters as part of normalization. One that doesn't leaves the ligature's own Unicode codepoint in the output. Most downstream tools, tokenizers, and search indexes simply don't recognize that codepoint as the letters it represents.

example

The oﬃce workﬂow relies on efficient filing

Unexpanded ligature glyphs (ﬃ, ﬂ) sitting inside otherwise normal words. A plain-text search for "office" or "workflow" won't match either one.

why-it-matters

An unexpanded ligature reads as one unrecognized character to word- and token-boundary logic. This quietly changes word counts, token counts, and search-matching near it.
A search or exact-match query for a word like "office" silently fails against text that still contains the ligature glyph for "ffi". The two are different codepoints even though a human reads them as identical.

how-to-check

Scan extracted text for the Unicode ligature block. It surfaces as a distinct, counted signal rather than something you'd have to spot by eye. Scan for unexpanded ligatures

related-terms

faq

Does an unexpanded ligature look wrong on the page?: No, it renders exactly as intended, since the ligature glyph is a legitimate part of the font. The problem only shows up in the extracted text, where the ligature's own Unicode codepoint isn't the letters it visually represents.
Will a search for a word with "fi" or "fl" in it match text containing the ligature glyph?: Not unless the ligature is expanded back to separate letters first. The ligature codepoint and the two-letter sequence it visually represents are different characters to a plain-text search, even though a human reads them as identical.

related-reading

Characters & encoding

See the term in real output.

Drop a file into the free reader and watch it happen.

Open the file reader →

Get an API key →