Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!inria!mirsa!daniel
From: daniel@mirsa.inria.fr (Daniel Dardailler)
Newsgroups: comp.windows.x
Subject: Re: XLFD matching
Message-ID: <567@mirsa.inria.fr>
Date: 28 Feb 90 08:33:46 GMT
References: <2845074091-1038891@RIGI>
Organization: Bull Research Center. Sophia Antipolis. France
Lines: 16

From article <2845074091-1038891@RIGI>, by Kimbrough@dsg.csc.ti.COM (Kerry Kimbrough):
> It seems that the spec doesn't really get down and define how OpenFont is supposed
> to match font names containing wildcards. Are we to assume that ? and * are
> to be treated as they are in Unix file name matching?

OpenFont is not supposed to match anything.
You must first use ListFonts with matching patterns and THEN use LoadFont
with a real fontname (one of those returned by ListFonts).
I'm currently working on a high level function (named ObtainFont), that 
will mask these tough mechanisms.

   Daniel Dardailler                   |      Email : daniel@mirsa.inria.fr  
   BULL  Centre de Sophia Antipolis    |      Phone : (33) 93 65 77 71       
         2004, Route des Lucioles      |      Telex :      97 00 50 F        
         06565 Valbonne CEDEX  France  |      Fax   : (33) 93 65 77 66      
				       |