Re: Continuing Font Problems: Some XFT fonts not using XFT engine?

[Taylor Venable <taylor@metasyntax.net>]

On Thu, Apr 16, 2009 at 08:40:42AM +0800, Jason Rumney wrote:
> Miles Bader wrote:
>> This isn't such a problem for most apps, which only understand one of
>> the two types of fonts, but it may terribly confuse Emacs, which can
>> handle both simultaneously.
>>   
>
> There should be an order imposed on font backends. So one backend should  
> always take precedence over the other, and duplicate font names should  
> not matter. It used to work that way, but it seems from reports of this  
> type that something has changed recently.

In my default-frame-alist I had set (font-backend . "xft, x") --
removing the "x" backend has prevented the use of the bitmap font.
This is fine for me since I only use one or the other, but it seems
that there could be a problem in stable precedence since I could
"randomly" get either a bitmapped or XFT font.

I should also note (if I haven't already) that I didn't see this
behaviour on my Ubuntu box at work, so I wonder (what with the several
problems I've had with fonts on OpenBSD) if it could have something to
do with some underlying font libraries.  I just checked and the bitmap
versions of those fonts are available on that machine as well.

Best regards,

-- 
Taylor Christopher Venable
http://real.metasyntax.net:2357/