Enhancing of UNIX typography with Fontconfig

Artjom Löbsack
Apr 2021


Refining our environment with beautiful fonts and their correct rendering.

~ 8 min
#unix, #fonts, #typography
Photo by Elisa Calvet B.


First of all, do not consider this text as a specific guide to action, it is rather my own thoughts on how to configure the unity of fonts in your system, and how to display them so that pleased the eye.

I believe that for a comfortable work, you can not do without high-quality typography, and that this moment should stand in the list of priority actions when customizing the working environment, since this primarily affects the overall impression and attractiveness of it.


Speaking about the “standard” display of text, I would like to mention the now popular "UNIX-like" OS, specifically macOS (and in general the OS family from Apple).

Their designers pay a lot of attention1 to typography issues, and it seems to me that they are quite good at it. Starting from developing fonts, and ending with writing engines for rendering text.

apple typography

Not least of all, the perception of text depends on the display itself on which the text is displayed, we can assume that some of Apple's success in this regard is due to their displays with high pixel density (PPI)2. But time goes on and now such matrices will not surprise anyone, so specific display parameters come into play.

Typeface, anti-aliasing, hinting, and so on, this is what today (in most operating systems) depends on - whether you will be comfortable working with text, or not.

Today I will try to fully cover my experience in configuring the display and selecting fonts in *NIX.


I would like to say right away that the selection of fonts is a purely personal matter for everyone, choose those families with which you will be comfortable working and which will please you with their appearance.

I, since we are talking about the "standard", will show you how to use the official fonts from Apple. They can be easily found on GitHub (don't worry, you can safely use them for non-commercial purposes).


You need to choose at least three fonts for three typefaces - Sans-serif, Serif, and Monospaced (all glyphs are the same width). I like SF Pro, Libertinus and SF Mono.

Download the fonts and put them in the ~/.local/share/fonts (or ~/.fonts) directory.


If you sometimes have to write some code (for example, you are engaged in software development :)), then you have probably heard about ligatures3 in monospaced fonts. These are special font glyphs that combine some adjacent characters into one.

For example, take a look at this line: -> => == != === ~~> и даже www. If your monospaced font supports ligatures, then you should see how the individual characters “merge” into one single one. Just in case, here's a picture:


It looks pretty enough, so I prefer to use fonts with ligatures, but what should I do if I really like a font and it does not support ligatures by its nature? The answer is simple - you need to patch it.

Don't be alarmed, it's simple. Especially if you use patching software, such as Ligaturizer. You can use it to add ligature glyphs from FireCode4 to your chosen font. Also in the process, you can choose which ligatures to use and which not to touch. Let's patch the monospaced SF Mono:

  • git clone git@github.com:ToxicFrog/Ligaturizer.git --recurse-submodules
    cd Ligaturizer
    mv ~/.local/share/fonts/sf-mono fonts

    pay attention to --recurse-submodules option!

  • Now you can select the ligatures you need by changing the file ligatures.py. Just comment out the lines with unnecessary ligatures.

  • Now we need to add our font to the build process by changing the file build.py:

    prefixed_fonts = ['fonts/sf-mono/*'
  • Run the build via make.

  • After successful patching, you will see the new fonts in fonts/output. These are the fonts we need, which now support ligatures. Move them to the font directory:

    mkdir ~/.local/share/fonts/sf-mono
    mv fonts/output/* ~/.local/share/fonts/sf-mono

More information here.


The Fontconfig library is responsible for the display in GNU/Linux and in many other UNIX-like operating systems.

You can make your own configuration via the configuration file, which is located at the path: ~/.config/fontconfig/fonts.conf. This is essentially a simple XML file. You can read more about setting up Fontconfig here.

Default font selection

Let's specify our installed fonts as the default fonts:

  <test name="family"><string>sans-serif</string></test>
  <edit name="family" mode="prepend" binding="strong">
    <string>SF Pro Display</string>

Here I pointed out that for the sans-serif family, I prefer the SF Pro Display font. To find out the internal name of a particular font, use the command: fc-list | grep 'SF Pro'. You will get a list of all fonts whose names contain the string 'SF Pro', the name is usually indicated after the colon: .local/share/fonts/sf-pro/SF-Pro-Display-Regular.otf: SF Pro Display:style=Regular, take only the part that is after the first colon and before the second, the rest is the font style.

I will also redefine the fonts for serif and monospaced:

  <test name="family"><string>serif</string></test>
  <edit name="family" mode="prepend" binding="strong">
    <string>Libertinus Serif</string>

  <test name="family"><string>monospace</string></test>
  <edit name="family" mode="prepend" binding="strong">
    <string>Liga SFMono</string>

To check the match, use fc-match. For example: fc-match serif will tell us: Liberationserif-Regular.otf: "Liberation Serif" "Regular", this means that we specified everything correctly and our font was applied, you can also check the other families.


There are also situations when we want to display our selected font instead of one, so add the following code to the configuration file:

  <family>Liberation Mono</family>

This construction must be added before defining our default fonts. Here I pointed out that instead of Liberation Mono, I want to use the standard monospace, which is pointed to SF Pro Display.


So, all the fonts are specified, the most important thing remains-to configure their correct display. To do this, add the following construction to the beginning in the <fontconfig> block (where we worked before):

<match target="font">
  <edit name="rgba"><const>rgb</const></edit>
  <edit name="lcdfilter"><const>lcddefault</const></edit>
  <edit name="hinting"><bool>false</bool></edit>
  <edit name="embolden"><bool>true</bool></edit>

These settings are common to all fonts in general, now I will explain what they mean:

  • rgba is responsible for sub-pixel mapping (better anti-aliasing).

  • lcdfilter filter for correct subpixel smoothing.

  • hinting aligns the glyphs on the grid. Disable it if you don't want the font to “jump”.

  • embolden synthetically thickens the outline. This is my favorite setting, because it makes any font look much cooler.

To learn about other options, visit the wiki or documentation. The documentation also contains a lot of interesting information about Fontconfig itself.

Use by programs


Usually, your terminal uses monospace as the font, so you should already have everything working. Otherwise, you will have to specify it manually. I'll show you how to change the font in st. Open the config file and add the following line:

static char *font = "monospace:pixelsize=15";

This approach saves us a lot of time, for example, if we want to change the font in different programs at once, we will have to change the font only in Fontconfig itself, and not in a bunch of different configuration files.

Here I only changed the font size (:pixelsize=15). You can override the font parameters right here, for example: "monospace:pixelsize=15:hinting=true" and so on.


Everything of course depends on your terminal emulator, but most likely the same scheme will be used there.


Here, too, everything should happen automatically, if this is not the case-see the example with the terminal, everything is exactly the same.



Open about:preferences, find the font settings, and specify Default everywhere.

I also prefer to change the font of the Firefox interface, via the userChrome.css file. It is located in ~/.mozilla/firefox/<profile>/chrome/userChrome.css, add it there:

* {
  font-family: sans-serif !important;


You can find out the name of your profile on the about:support page, in the Profile Directory field.


Open chrome://settings/fonts, and specify:

Serif font Serif
Sans-serif font Sans
Fixed-width font Monospace

Icons and emojis

To display various Unicode icons, you will need an icon font, such as Nerd Fonts. Check out this repository, it contains a huge number of icon fonts, and there are also utilities that allow you to patch your font to support icons in it.

Emojis are essentially also some font, so they can also be redefined in Fontconfig. So for example, to use an Apple emoji, install this font. Then go to ~/.config/fontconfig/fonts.conf:

  <test name="family"><string>emoji</string></test>
  <edit name="family" mode="prepend" binding="strong">
    <string>Apple Color Emoji</string>



So, I showed you how to configure and select fonts using Fontconfig. Do not be lazy and study the documentation for it. I guarantee - you will not regret it, because it contains much more interesting than this article. I tried to show you the basic principles of settings, and a general idea of typography in *NIX. I hope it was informative :).

My configuration can always be found here5

Article reference.