The fontconfig library is intended to provide uniform font selection and configuration amongst all GUI applications. Even though it is common for various desktop environments to provide their own font overrides and configuration, still fontconfig is the underlying library.
- 1 Configuration
- 2 Anti-aliasing, hinting and sub-pixel rendering
- 3 Infinality
- 4 Picking fonts
- 5 External resources
fontconfig uses XML files in /etc/fonts/ directory to generate its internal configuration. By default it parses /etc/fonts/fonts.conf (users should not edit this file!) which sets some sane defaults and usually contains code to also parse /etc/fonts/conf.d/ content. In addition there is /etc/fonts/conf.avail/ directory that contains various possible configuration files that each cover some aspect of fontconfig. It's customary to symlink necessary files to /etc/fonts/conf.d/. These files are executed in order they are named, for this reason their names start with a two digit number with the first (tens) indicating class, that is, what the file affects.
Gentoo specific way
Gentoo ships an eselect module (eselect fontconfig) that does exactly what was described in generic way - it manages symlinks of files in /etc/fonts/conf.avail/ by adding or removing them from the /etc/fonts/conf.d/ directory. For obvious reasons changing system wide configuration requires appropriate permissions.
Listing available files
Enabling a file
Files can be enabled either by filename or by the number in brackets. These two do the same thing:
Disabling a file
Files can be disabled likewise:
Custom system wide configuration
Enable 51-local.conf and create /etc/fonts/local.conf (this is an XML file, you have been warned).
Enable 50-user.conf (possibly enabled by default). And use ~/.fonts.conf (same format as local.conf)
You can check the default font replacement, for example for Arial, by typing:
Anti-aliasing, hinting and sub-pixel rendering
Anti-aliasing is enabled by default and makes fonts less blocky. Hinting is an attempt to cope with the low pixel count per unit of area of current displays. Correct hinting makes characters more crisp but since font metrics aren't changed (and arguably should not change) affects how overall the rendered text looks like. Sub-pixel rendering uses the fact that LCD matrix has three primaries to effectively triple the resolution of text but can make characters appear not entirely black. To combat that lcdfilter is to be used with sub-pixel rendering (available for newer fontconfig) but it can blur the characters too much. In the end this entirely depends on person how they like their text.
The default fontconfig behaviour regarding hinting is unknown [personal note: what is this madness, how can one of the key components of Linux graphical stack be unknown?!] but it can be made deterministically sub-optimal by making a system wide default.
- First enable /etc/fonts/local.conf
- Edit the file to include full hinting by default
Using sub-pixel rendering
It's important to determine the sub-pixel layout of the LCD matrix. It's usually RGB (10-sub-pixel-rgb.conf) but the only way to be sure is to either consult display specification or use this sub-pixel layout test to determine it. Once determined, enable the appropriate 10-sub-pixel-<matrix type>.conf file.
It's strongly advised that lcdfilter, if available, is used with sub-pixel rendering. It comes in different varieties but the default (11-lcdfilter-default.conf) should be appropriate for all common fonts.
Autohinter attempts to do automatic hinting disregarding any existing hinting information. Until recently it was the default because TrueType2 was covered by patents but now that they have expired there's very little reason to use it. From technical point of view it does better than broken or no hinting information but it will be strongly sub-optimal for fonts with good hinting information. Generally system fonts are of the second kind so autohinter should not be used.
Infinality is a somewhat controversial set of patches for FreeType and accompanying fontconfig files. The goal of Infinality is to provide higher quality font rendering including emulation of other OS font rendering styles. It's at best of beta quality but newer FreeType ebuilds have a USE flag for enabling Infinality. It should be kept in mind that some fonts can be rendered worse than with vanilla FreeType and furthermore Infinality is known for making applications crash under certain conditions.
Enable the 'infinality' USE flag by editing make.conf either manually or by using euse tool.
And then rebuilding affected programs.
Unless messages shown after rebuild tell otherwise, enable 52-infinality.conf.
Infinality can be configured in various ways including custom configurations but easiest is to use pre-made profiles shipped in media-libs/fontconfig-infinality that along with eselect modules should have been installed as dependencies of infinality USE flag.
Quick and reasonable config
It's also recommended to disable all fontconfig settings except for 52-infinality.conf as they interfere with the rendering of infinality styles:
Certain fontconfig settings do not interfere with how the fonts are rendered, but rather determine the default fonts for font-types (such as Monospace, sans-serif, etc.). Such settings (for example the 62-croscore-*.conf configurations) can be left enabled.
Infinality provides FreeType environment variables that can be used to configure features introduced with its patches as well as fontconfig files to be used with these changes. Fontconfig file sets are administrated on Gentoo via eselect infinality while the FreeType behaviour is set using eselect lcdfilter.
These eselect modules function as usual. Listing available fontconfig file sets.
Listing available FreeType variable sets.
Both sets should match of course except when there are multiple matches possible such as shown below.
Choosing the right font can be trickier than deciding on the right hinting type.For one reason or another fonts will not be perfect but it's certainly doable to make that same fonts look better than, say, Windows 7 default font configuration. The following information is biased but it can't be helped.
|DejaVu (media-fonts/dejavu)||Many styles, covers a lot of code points||Exceptionally wide - even condensed is wider than same height monospace (not to mention average sans-serif font), overall second to Verdana (an MS font) in width.|
|Droid (media-fonts/droid)||Covers a lot of code points and scripts||Very dry, wide yet thin glyphs is probably the most memorable aspect of Droid font family. Clearly designed with handheld devices and their small screens in mind.|
|Gentium Plus (media-fonts/sil-gentium)||Fairly distinctive, might appeal to people who like narrow fonts||Only serif, as with other SIL fonts hinting is questionable.|
|Liberation (media-fonts/liberation-fonts)||MS TrueType core font metric compatible, overall look pretty decent||Few fonts seem to have hinting trouble.|
|Ubuntu (media-fonts/ubuntu-font-family)||A distinctive font with style which might not appeal to everyone, overall looks good as well as covering a fair bit of code points.||Only default sans-serif is truly polished, narrow and monospaced versions are unfinished. No known serif font that would accompany it well.|
|URW (media-fonts/urw-fonts)||Metric compatible with popular Adobe fonts (among others?)||Seem to require slight hinting.|
|MS TrueType core fonts (media-fonts/corefonts)||Includes most fonts used in documents or on web (as of 01.07.2012 Gentoo only has an old version without Tahoma)||MS does not distribute them nowadays so the available fonts are from many years ago and might not reflect the current state of them. Obviously lacks fonts introduced later. Seem to require full hinting.|
|Unifont (media-fonts/unifont)||Covers a lot of code points.||In addition to being ugly as sin it also fails basic requirements to be considered a typeface - is it sans-serif, is it serif? Please never use this.|