Path: utzoo!attcan!uunet!husc6!mailrus!ncar!boulder!stan!garya
From: garya@stan.com (Gary Aitken)
Newsgroups: comp.windows.x
Subject: Re: default font
Message-ID: <292@stan.com>
Date: 12 Dec 88 18:58:32 GMT
Organization: Solbourne Computer Inc., Longmont, Co.
Lines: 16

In thinking about it further, there is no reason you shouldn't be able
to do any operation you want with the default font.  One is allowed to
obtain the XFontStruct for a default font; from this structure and the font
properties one should be able to ascertain whether or not it is suitable.  In
particular, the FONT property contains information from which one can
determine whether or not the font has the proper ISO encoding.  Although,
unfortunately, the current "fixed" default font has a FONT property which
doesn't contain encoding info.  But one could easily add the 5 or so 
"nonconforming" fonts to the code which checked the font properties.

In light of this, wouldn't it solve a lot of problems if the server DID
allocate a font id for default fonts?  Is there any reason not to?  It
requires no protocol changes; the main problem as I see it is that the
fid member of the XFontStruct returned from an XQueryFont using a default
GC is currently a GC id, not a Font id.  Is this done for a purpose,
or is it a relic?