<quote who="Christopher Vance"> > I'm trying hard to use as little GNOME-related stuff as possible, but > don't seem to have been able to avoid it totally. :-(
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. > Okay, so it's the thin client installation of fontconfig I have to fix. I think you missed the point, unless you're running software *on* the thin client (which itself is the X server). Because fontconfig is used on the application client side, you do not need to fix it on the display terminal, you need to fix it on the application server. > Given a lack of /etc/init.d stuff, do I need to do anything to teach > fontconfig about the content of the new font directories? 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. - Jeff -- linux.conf.au 2007: Sydney, Australia http://lca2007.linux.org.au/ "Microsoft treats security vulnerabilities as public relations problems." - Bruce Schneier -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
