I wish I could say it was a rewarding experience, alas, I cannot. At least not without descending into maniacal laughter for a few moments.
One of my personal quirks is an inability to let something go. Especially if it’s computer related. Being unable to just let-it-go has it’s pluses as minuses. On the plus side, I’ve solved some pretty tricky computer related problems and learned some interesting lessons along the way. On the minus side, I can waste hours working the problem, finding a solution and feel like I’ve wasted that time.
This experience goes in the minus column.
That said, I figure I’ll just pass this along so that some other poor sap doesn’t get caught up in the mess I got caught in. If I can save someone a few hours from their life, I suppose I’ll have salvaged something. Hopefully they find it prior to wasting hours of their life on the problem.
To install ProFont, untar it into a `/usr/local/share/fonts/profont’ directory. Then zip all the files using gzip:
gzip /usr/local/share/fonts/profont/*
Now, as root, create the file /etc/fonts/local.conf
and fill it with the following gibberish:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<selectfont>
<acceptfont>
<pattern>
<patelt name="family"><string>ProFont</string></patelt>
</pattern>
</acceptfont>
</selectfont>
</fontconfig>
This is important because this file makes the font visible to the fontconfig subsystem. The crux of the problem is that bitmapped fonts, what ProFont is, are disabled by default. Finally, as root, enter the command:
fc-cache -fv
Watch the output. Check for a line with the ‘profont’ directory in it and make sure that it does not read 0 fonts, 1 dir
at the end. If it does, go back up a couple of paragraphs and try again. In my case, it read 7 fonts, 1 dir
and it seems likely that’s what your output should be as well. Unless you’ve removed some of the sizes, or added them.
Do NOT put this file into /etc/fonts/conf.avail
as a numbered file. Do NOT put this file into /etc/fonts/conf.d
. Do NOT monkey with the xset
command- it will not get you anywhere. Do NOT bother with mkfontdir
. Do NOT bother fonts.dir
, fonts.alias
or encodings.dir
files.` I’m sure there are some other things that you DON’T need to bother with- I’ve just forgotten them at this point.
One last thing. If you’re using ROXTerm as your terminal emulator and the font doesn’t look right after selecting it, close down that terminal and restart it. Not X itself, just the terminal. On my system, the spacing was completely botched when I first selected it and I was just about to stick my head through my monitor. Fortunately, my hands slamming down on the keyboard closed my terminal, didn’t damage my keyboard and distracted me from the head-through-monitor thing. When I opened a new one terminal, everything looked just fine.
I was hoping for a sense of relief. Instead, all I’ve got is this blogpost.
UPDATE: If you try to install something like the proggy font, make sure you unzip the ‘pcf’ file- don’t leave it in the gz
file. For some reason fontconfgi
doesn’t like it that way. Everything from above still applies. Although, truth be told, the TTF version works better on my setup and none of the config file fiddling is needed. Just install the files to the directory and then us the fc-cache
command.
7 replies on “Installing ProFont on Debian”
I’ve used this several times, so don’t feel like you’ve wasted your time. It’s been very helpful :).
Glad it’s been of use. I hadn’t read that post in awhile. Having re-read it, I’m glad I wrote it down because it seems exceedingly unlikely I’d be able to retrace my steps to figure it out again. Blogging: +1
Also- don’t know if you submitted a url when you commented, but I tried some software out for getting your comment out of moderation and it botched your info. Luckily, I still had your name and email so I could re-enter those. Anyway, if you email it or leave it in a subsequent comment, I’ll correct my mistake.
Thanks for the comment, stop by again some time.
How do you know what string to match against for family? I have a PCF font I want to install (http://www.eurogaran.com/downloads/lispmfont/), but I don’t know what its family is.
I just followed the filename that was copied into the font directory.
I’ve tried that myself with a few variations using the
lispmfont.tgz
download you pointed out and have been unsuccessful so far.I’ll investigate a little more to see if I can come up with anything.
UPDATE: Hmm. For whatever reason, the file doesn’t seem to be recognized using the technique in this post. The family type is “Fixed” btw- I figured that out by opening the file and taking a peek.
That said, follow the instructions here, it seems to have worked for me, but the font doesn’t render very well. At least, there’s a font named “Fixed” that appears in my font selection.
I wasn’t able to make your fix work, (probably because I’m sitting on crunchbang.) However, I did make it work by going for the .ttf version of Profont and placing it in
~/.fonts
And running these lines in the terminal
fc-cache -fv
and
fc-list
to first re-cache fonts, and then spot whether or not the font was found.
Thanks for doing this writeup, and a second thanks for the advice to steer away from potential pitfalls.
You’re welcome- glad it was able to help you figure things out.
I’d never heard of ‘crunchbang’ before. Looks interesting, thanks for the tip.
You can enable bitmap fonts on Debian by running:
dpkg-reconfigure fontconfig-config
(select to enable bitmap fonts on the debconf dialogue) Then…
dpkg-reconfigure fontconfig