Well, I got home without running over anybody, and the cat got her insulin in time... And the X server has been restarted several times today (on my office computer, where everything was going wrong). So, what you seem to be saying -- as I read between the lines -- is that KDE is all show, and no go. It just pretends to be able to install fonts, but it doesn't even bother to do a necessary step, running "xset", but it doesn't bother mentioning it. All it would take is a simple: "You are finished with KDE font operations. Now, you must run the xset command to tell the underlying X server what you just told KDE". I mean, how difficult is it to put in a text pop-up at the end of an update function? Wonderful. If somebody is going to just plain fail to do the job, and somebody else is going to fail to do the job, but make a big show of pretending that they are doing it... give me the one that's honest about it... at least, I'll know where I stand. Maybe it's time to look into Icewm or Blackbox, and get away from a desktop that obscures X without covering all of X's requirements and functions. And yes, I looked at the KDE Help and FAQ and... and... Tomorrow, somebody will point out what I've foolishly missed, and I'll have to apologize to the KDE developers... or not. /kevin On Thursday 03 October 2002 01:43, Christopher Mahmood wrote:
I know nothing about kde or the way it handles fonts (or openoffice) but in general when you add new fonts you need to restart the X server or at least update the font path with xset.
--
-ckm
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
-- "DIRty DEEDS, and they're DONE dirt cheap." [Sing it with me, now...]