Article View: comp.windows.x
Article #37594XLFD matching
From: ekberg
Date: Tue, 27 Feb 1990 15:39
Date: Tue, 27 Feb 1990 15:39
25 lines
1551 bytes
1551 bytes
Kerry,
> 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?
From the X11R4 protocol specification describing OpenFont:
This request loads the specified font, if necessary, and associates
identifier fid with it. The font name should use the ISO Latin-1 encoding,
and uppercase and lowercase do not matter. The interpretation of
characters ``?'' (octal value 77) and ``*'' (octal value 52) in the name is
not defined by the core protocol, but is reserved for future definition. A
structured format for font names is specified in the X Consortium standard
``X Logical Font Description Conventions''.
Fonts are not associated with a particular screen and can be stored as a
component of any graphics context.
This says to me that X11R4 version of OpenFont should treat the ``*'' and ``?''
characters as ordinary characters, but that the X11R5 version may specify
alternate meanings, such as the one that you suggest.
-- tom (aisle C-4Q), ekberg@csc.ti.com
Technical Details
Message-ID:
<9002271539.AA18833@osage.csc.ti.com>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!ogicse!mintaka!bloom-beacon!ti-csl.csc.ti.COM!ekbergReferences:
<2845074091-1038891@RIGI>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!ogicse!mintaka!bloom-beacon!ti-csl.csc.ti.COM!ekberg From: ekberg@ti-csl.csc.ti.COM Newsgroups: comp.windows.x Subject: XLFD matching Message-ID: <9002271539.AA18833@osage.csc.ti.com> Date: 27 Feb 90 15:39:34 GMT References: <2845074091-1038891@RIGI> Sender: ekberg@osage.csc.ti.com Organization: The Internet Lines: 25