SLUG Mailing List Archives
Re: [SLUG] fontconfig q
- To: slug@xxxxxxxxxxx
- Subject: Re: [SLUG] fontconfig q
- From: "Christopher Vance" <cjsvance@xxxxxxxxx>
- Date: Mon, 21 Aug 2006 10:33:54 +1000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oVlGOayNIHsar1I7vyE3o11dqbaxfSozmkHH2nonx+bScuZ7pN+KKcD4Lif57nIkZ3Gv/2Zzx80RsjD03ST/kqyq5ZPDXXbmGTCADStkEyMBtzm3Zt3ZdeCGIlE0pMdugerNn8fGgz3x3b//SDClq+zKqGDKZCdQtDbKAAsPepc=
On 8/21/06, Jeff Waugh <jdub@xxxxxxxxxxxxxx> wrote:
I mentioned GTK+ in my explanation, but all modern toolkits do it the same
way. None of this is GNOME specific, it's all infrastructure. Not sure why
you need to avoid it though, it's perfect for the thin client / application
server use case.
I had assumed the G in GTK+ meant GNOME, but accept the correction.
May I should have said "diskless", rather than "thin". Most
aplications run on the diskless thing -- there is no application
server. Most of the OS is a readonly squashfs, and most nfs access is
also readonly. The main app is a biggish thing in Tcl/Tk, which is
happy using the fonts off xfs. Firefox gets used comparatively little.
Only four pcf font files out of /usr/X11R6/lib/X11/fonts/misc are
local. These don't yet appear in fc-list, so I have work to do.
System font directories that fontconfig knows about will need generated
cache files (your distribution should do this for you, but if not, look into
fc-cache). Local font directories will recache themselves when required.
Unfortunately, I am the distribution, as there is no fontconfig
shipped with thinstation so far. :-(
I'll check fc-cache, and try to decide whether directories need to be
copied into a writable memory fs, or whether they can be preconfigured
on the readonly nfs, served off OpenBSD.