FONTCONFIG
Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.
fontconfig fonts.conf Preview.
At a glance
| Purpose | A fontconfig configuration file (fonts.conf): XML that sets font directories, aliases and matching rules. |
| Extensions | .fontconfig |
| Poka parser | poka-fonts-conf |
| Viewer | poka-metadata-card-viewer |
| Depth tier | Metadata card (see Depth tiers) |
| Breadth tier | B4 Summary (see Breadth tiers) |
How much Poka reads
B4 Summary. The container and metadata are read and summarised (counts, properties, structure), but the main content is not rendered.
Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-fonts-conf/src/main.rs (232 lines) and plugin.json. No unit tests or tests/samples.rs; the corpus has no .fontconfig, .fonts.conf and .fonts-conf sample. Covers .fontconfig, .fonts.conf and .fonts-conf. The card counts directory, cache-directory and include elements (with samples), match blocks, test and edit elements, edit modes, alias blocks, prefer, accept and default lists, family uses, selectfont blocks and glyph accept and reject rules, by matching text. Judgement: B4: the configuration is summarised by counts, but its rules are not shown.
What Poka does not read
- The rules are not shown: which families are aliased or preferred, and what each match does
- Elements are counted by text matching, not parsed as XML
- Included files and directories are not followed
- Files over 8 MiB are cut (flagged)
Libraries
Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.
- fontconfig-parser (candidate; MIT; Rust; https://github.com/Riey/fontconfig-parser) — Parses fonts.conf via merge_config; README says not all features are implemented
Sources
- parsers/poka-fonts-conf/src/main.rs
- parsers/poka-fonts-conf/plugin.json