[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 98338] Fonts installed by KControl are not cached
From: Craig Drummond <Craig.Drummond () gmx ! net>
Date: 2005-02-01 21:19:34
Message-ID: 20050201211934.5512.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=98338
------- Additional Comments From Craig.Drummond gmx net 2005-02-01 22:19 -------
The font-installer from KDE3.3 installs fonts int $HOME/.fonts. The installer
from 3.1 and 3.2 installed into $KDEHOME/share/fonts/TrueType (truetype
fonts) or $KDEHOME/share/fonts/Type1 (for postscript fonts). Any fonts still
in $KDEHOME/share/fonts/TrueType are still listed - so that fonts are not
"lost" ($HOME/.fonts as this seems to be fontconfig's preferred font
location)
When any new fonts are installed - which would be into $HOME/.fonts - then
fc-cache *is* executed.
Can you confirm where a newly installed font is being placed? i.e. install a
font, this *should* go into $HOME/.fonts Look into this directory, and have a
look at the "fonts.cache-1" file. This file is created by fc-cache, and it
should list the new font. (Note that fc-cache is not called immediately, and
it may be some 5 seconds after the font is installed before it is called)
Thanks.
Craig.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic