Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucsd!ucsdhub!hp-sdd!hp-pcd!hpcvlx!ken
From: ken@hpcvlx.cv.hp.com (Ken Bronstein)
Newsgroups: comp.windows.x
Subject: Re: XLFD matching
Message-ID: <100920178@hpcvlx.cv.hp.com>
Date: 28 Feb 90 00:32:44 GMT
References: <2845074091-1038891@RIGI>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 12


Much of the the semantics for XLFD are not documented (or still being
debated) especially in light of scalable font technology.  I can't
speak for the SUN implementation in detail BUT the wild cards are
intended to be resolved with the first matching font,  where the
order of the fonts is reflected by the order of the returned names
from the XListFonts function.  As expected * matches any string, while
? matches any character.

Note that worse semantic debates can be made regarding the meaning of
requesting fonts of point size zero with outline font files; or other
stuff that is now being hammered out in the MIT X font working group.