Re: What happened to B&H Lucida fonts?

On Sat, 2004-03-27 at 04:45, David Krider wrote:

> You know, red-carpet. I just freshened up everything in XD2 (running on 
> SuSE 9.0) that was out of date, which was mainly Galeon, Mozilla, 
> OO.org, and fontconfig. (Admittedly, I also updated to the -199 kernel, 
> and the new versions of openssh and openssl at the same time, but that 
> shouldn't have caused any problems.)

That is weird then. To look at what files Xft/fontconfig can see open
Nautilus and type in the location bar the uri fonts:///. On my RHL9+XD2
machine I can see Lucida Sans Typewriter, Lucida Sans Typewriter Italic,
Lucida Sans Typewriter Semi-Bold, and Lucida Sans Typewriter Semi-Bold
Italic. Unfortunately I have no idea which package installed those fonts
on my system.

These fonts are also visible to Xfs. In a terminal, if I do

xlsfonts | grep -i '\-b&h\-lucidatypewriter'

then I get the fonts listed in all their various charsets. 

> > I don't believe the fontconfig package contains any fonts itself, so
> > downgrading or upgrading it wouldn't make any difference.
> 
> Well, I thought the same thing, but that's the only thing I noticed 
> before I upgraded that seemed to have anything to do with fonts.

Have you tried running "fc-cache -fv"? (You might want to run that once
as root and once as you.)

> Not to be argumentative, but I think that, while it's nice and all, it 
> sucks in comparison, especially in apps like gnome-terminal. This one 
> issue has driven me back and forth between windowing environments more 
> than once. It's even what caused me to give up on trying Debian and 
> settle on SuSE!

Fair enough!

> I don't know what other information to give,

Not sure either. I'm assuming that there is no way the upgrade could
have actually removed the fonts from your system. So for some reason
Xft/fontconfig aren't seeing them. One possibility is that the fonts
didn't come with your system and instead you installed them yourself in
some directory, which you then manually added to /etc/fonts/fonts.conf,
and that file has been overwritten by the upgrade (although it shouldn't
have -- RPM is meant to not overwrite altered config files but instead
save the new one as /etc/fonts/fonts.conf.rpmnew). Another possibility
is that your font-cache has gotten all screwy after the upgrade.
Hopefully fc-cache -fv should sort that out, although as a last resort
you could try logging out and logging back in again. (I hate giving
advice like that -- it's hardly ever necessary. It makes it sound like
Windows -- "You've installed a program. You must now restart your
system!")

Best, Darren

-- 
=====================================================================
D. D. Brierton            [email protected]          www.dzr-web.com
       Trying is the first step towards failure (Homer Simpson)
=====================================================================

_______________________________________________
Users maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/users