bug#3319: 23.0.93; Default font

[Kenichi Handa <handa@m17n.org>]

In article <jwvvdnwwmcc.fsf-monnier+emacsbugreports@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> Breaking backward compatibility might be OK, but I still wonder: how
>>> come we ended up with "Sanvito Pro Subhead" from a spec of
>>> a non-existing "outline-lucida sans typewriter"?

> > When there's no font of the specified family, Emacs tries to
> > find a font without specifing family.   In that case, which
> > family is selected is just arbitrary.

> Shouldn't we fallback on the default font families
> (Sans/Courier/...) instead?

It sounds good, but the proper fallback font family is
different on platforms.  For instance, xfns.c has this code:

      char *names[]
	= {
#ifdef HAVE_XFT
	    /* This will find the normal Xft font.  */
 	    "monospace-12",
#endif
	    "-adobe-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-1",
	    "-misc-fixed-medium-r-normal-*-*-140-*-*-c-*-iso8859-1",
	    "-*-*-medium-r-normal-*-*-140-*-*-c-*-iso8859-1",
	    /* This was formerly the first thing tried, but it finds
	       too many fonts and takes too long.  */
	    "-*-*-medium-r-*-*-*-*-*-*-c-*-iso8859-1",
	    /* If those didn't work, look for something which will
	       at least work.  */
	    "-*-fixed-*-*-*-*-*-140-*-*-c-*-iso8859-1",
	    "fixed",
	    NULL };

and w32fns.c has this:

      static char *names[]
        = { "Courier New-10",
            "-*-Courier-normal-r-*-*-13-*-*-*-c-*-iso8859-1",
            "-*-Fixedsys-normal-r-*-*-12-*-*-*-c-*-iso8859-1",
            "Fixedsys",
            NULL };

---
Kenichi Handa
handa@m17n.org