Unrecognized font family
fontfamily names a value that isn't a font-registry key. Keystone warns and,
on PDF and EPUB, falls back to its default, so a lenient build still produces its
artifact; under strict mode it stops.
What it looks like
fontfamily: garmond
WARN: fontfamily 'garmond' is not a registry key; using the default (latin-modern). See https://keystone.knight-owl.dev/writing/typography/
What it means
fontfamily must name a font in the registry — a
built-in font or one you've
registered. On PDF and EPUB, an
unrecognized value falls back to the default (latin-modern), which keeps output
stable across engine and Pandoc versions. DOCX and ODT take their fonts from the
reference document, so there is no fallback — the warning drops the
using the default note.
How to fix
Check the spelling against the built-in fonts, or register the font if it's your own.
Related
- Unsupported font size — the same warn-and-fall-back
shape for
fontsizerather thanfontfamily.