This line tells you that fontconfig is simply ignoring the font. It
would be interesting to see what would happen if you placed a true type
font there.
It works with true-type version of the same font (from this url:
http://www.proggyfonts.com/index.php?menu=download):
$ ls -l ~/.fonts
-rw-r--r-- 1 mike mike 83 2007-02-06 06:37 fonts.dir
-rw-r--r-- 1 mike mike 21024 2007-02-03 15:35 ProggyClean.pcf
-rw-r--r-- 1 mike mike 41208 2007-02-07 15:15 ProggyClean.ttf
$ fc-cache -vf ~/.fonts/
/home/mike/.fonts/: caching, 1 fonts, 0 dirs
/var/cache/fontconfig: not cleaning unwritable cache directory
/home/mike/.fontconfig: cleaning cache directory
fc-cache: succeeded
$ fc-list | grep -i proggy
ProggyCleanTT:style=Regular
All I can suggest now is that you copy the font to one of the
system directories listed when you run 'fc-cache -vf' (without a
directory argument). Seems a lot of trouble to go to just to use a font,
doesn't it? Fortunately, defoma does all this work for you in the case
of official Debian font packages.
The reason I wanted to use pcf font is because ttf version does not
display correctly on one of the machines where I'd like to use it. Is
there any way that I can diagnose where the problem is? Any sort of
error log that font systems keeps?
Also, the font system in linux is complex. As I understand, font
handling can happen inside X itself, inside Xft and with Xfs server.
Is there any reason why three different system components are
responsible for fonts? What are the pros/cons of each one and where
can I find more information about each?
Thank you.
-Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
