fc-cache - build font information cache files
fc-cache [ -EfrsvVh ] [ --error-on-no-fonts ] [ --force ] [ --really-force ] [ -y dir | --sysroot dir ] [ --system-only ] [ --verbose ] [ --version ] [ --help ] [ dir ... ]
fc-cache scans the font directories on the system and builds font information cache files for applications using fontconfig for their font handling.
If directory arguments are not given, fc-cache uses each directory in the current font configuration. Each directory is scanned for font files readable by FreeType. A cache is created which contains properties of each font and the associated filename. This cache is used to speed up application startup when using the fontconfig library.
Note that fc-cache must be executed once per architecture to generate font information customized for that architecture.
This program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below.
- -E --error-on-no-fonts
- Raise an error if there are no fonts in dir or directories in the configuration if not given.
- -f --force
- Force re-generation of apparently up-to-date cache files, overriding the timestamp checking.
- -r --really-force
- Erase all existing cache files and rescan.
- -s --system-only
- Only scan system-wide directories, omitting the places located in the user's home directory.
- -v --verbose
- Display status information while busy.
- -y -sysroot dir
- Prepend dir to all paths for scanning.
- -h --help
- Show summary of options.
- -V --version
- Show version of the program and exit.
- Directory to scan for fonts.
fc-cache returns zero if the caches successfully generated. otherwise non-zero.
- These files are generated by fc-cache and contain maps from file names to font properties. They are read by the fontconfig library at application startup to locate appropriate fonts.
The fontconfig user's guide, in HTML format: /usr/share/doc/fontconfig/fontconfig-user.html.
This manual page was written by Keith Packard <email@example.com> and Josselin Mouette <firstname.lastname@example.org>.
|27 January 2023|