Re: No XFT in CVS from this morning

[Kenichi Handa <handa@m17n.org>]

In article <20080618064209.5bee6ca7.taylor@metasyntax.net>, Taylor Venable <taylor@metasyntax.net> writes:

> On Wed, 18 Jun 2008 12:52:10 +0900
> Kenichi Handa <handa@m17n.org> wrote:

> > In article <20080617224331.57adb1e2.taylor@metasyntax.net>, Taylor
> > Venable <taylor@metasyntax.net> writes:
> > 
> > > > % emacs --xrm 'Emacs*FontBackend: xft x'
> > 
> > > I get: "No font backend available" both with and without "-Q".
> > 
> > Oops, sorry, this is the correct form:
> > 
> > % emacs --xrm 'Emacs*FontBackend: xft,x'

> Great!  That fixes it.  I guess perhaps the equivalent Lisp code when
> put into the .emacs file doesn't get read early enough to take effect
> on the first frame?

It seems so.

> > xfont-list: -*-DejaVu Sans Mono-*-*-*-*-*-*-*-*-*-*-iso8859-1
> >   -misc-dejavu sans mono-medium-r-normal--12-*-75-75-m-*-iso8859-1
[...]
> > ftfont-list: -*-DejaVu Sans Mono-*-iso8859-1
> >   -unknown-DejaVu Sans Mono-bold-normal-normal-*-m-0-iso8859-1

Hmmm, when Emacs starts, it uses X font which has "misc"
foundary, and Emacs remembers that.  Later, when the
font-backend order is changed, Emacs still prefer a font of
"misc" foundary.  And, unfortunately, fontconfig returns
that same font with "unknown" foundary.

It seems that we must remember somehow which font properties
are actually specified, and which are just extracted from
the selected font.

---
Kenichi Handa
handa@ni.aist.go.jp