Re: (re)display problems after font backend merge

[Stephen Berman <Stephen.Berman@gmx.net>]

On Fri, 23 May 2008 22:57:10 +0100 David De La Harpe Golden <david@harpegolden.net> wrote:

> Stephen Berman wrote:
>
>> -Adobe-Adobe Helvetica-normal-normal-normal-*-12-*-*-*-*-*-iso8859-1
>> 
>> The output includes Adobe Helvetica but not the other two fonts above
>> (though B&H Lucida, B&H LucidaBright, and B&H LucidaTypewriter are
>> listed).
>>
>
> I guess the filenames all ended in .pcf or .pcf.gz ? 

Yes.

>                                                      If so, they're all
> fonts that ship as bitmaps with X. Yours apparently have the foundry
> names prepended in the family though, which might be some sort of policy
> change that I haven't encountered yet.
[...]
> But - bah. That "helv" (rather than "helvetica") that is in emacs'
> variable-pitch's family by default is IMO unlikely to do anything
> particularly sensible (unlike the "courier" default in fixed-pitch) -
> "helv" is neither the name of a font nor an alias in fontconfig as far
> as I can see, and family matching is not AFAICS substring-based in
> fontconfig.
[...]
> *** So perhaps emacs should default to "helvetica" for variable-pitch
> if it's gonna default to "courier" for fixed-pitch.   Then fontconfig
> might have a chance. :-)

I tried both "Helvetica" and "Adobe Helvetica" but didn't notice any
difference from just "helv".  However, after adding the x font backend
(as well as xft), the mode-line-inactive and tabbar-default faces did
get realized with Helvetica font (not anti-aliased).

Steve Berman