Skip to content

Instantly share code, notes, and snippets.

@burningTyger
Created December 6, 2014 13:24
Show Gist options
  • Star 7 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save burningTyger/a523ab41ef809d05e9fb to your computer and use it in GitHub Desktop.
Save burningTyger/a523ab41ef809d05e9fb to your computer and use it in GitHub Desktop.
Arch better looking fonts for Chrome
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target='font' >
<edit mode='assign' name='rgba' >
<const>rgb</const>
</edit>
</match>
<match target='font' >
<edit mode='assign' name='hinting' >
<bool>true</bool>
</edit>
</match>
<match target='font' >
<edit mode='assign' name='hintstyle' >
<const>hintslight</const>
</edit>
</match>
<match target='font' >
<edit mode='assign' name='antialias' >
<bool>true</bool>
</edit>
</match>
<match target='font'>
<edit mode='assign' name='lcdfilter'>
<const>lcddefault</const>
</edit>
</match>
</fontconfig>

#Font rendering fix for Arch

Some apps in Arch have difficulties in rendering fonts. This Gist might help you to fix this issue. This is a combination of information I have found so far on the interwebs. Most importantly from here: http://kaslnetwork.com/articles/making-ugly-fonts-pretty-in-arch-linux/

I have then applied the comment on where to put the file and also fixed the double quotes to single quotes which caused an error on my system.

Do the following with 29-prettify.conf:

sudo mv 29-prettify.conf /etc/fonts/conf.avail/29-prettify.conf

This will move the file to its destination - you need root permissions for that.

Then link it as well so it's picked up:

 sudo ln -s /etc/fonts/conf.avail/29-prettify.conf /etc/fonts/conf.d/29-prettify.conf

Now you need to restart X (Gnome or whatever you're using). You can usually do it by saving your documents and logging out from your session or by pressing ctrl+alt+del. But beware, this will close all open apps. Make sure you've saved everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment