Path: utzoo!attcan!uunet!convex!killer!ames!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!bloom-beacon!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Font Properties
Message-ID: <19880901011505.7.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 1 Sep 88 01:15:00 GMT
References: <15670@shemp.CS.UCLA.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 28


    Date: 31 Aug 88 17:25:35 GMT
    From: tek@CS.UCLA.EDU

    Some fonts seem to have properties not listed in the table in the Xlib 
    manual.

Right.  There is no requirement that fonts only have "well-known" properties,
the property mechanism is there explicitly to allow an open-ended set.

    By looking at my Xatom.h, I determined two of these "out of
    table" properties were XA_COPYRIGHT and XA_FAMILY_NAME.

Well, "xprop -font <font>" could have given you this alot easier.

    Font properties are supposed to be just one 32 bit number. 

Right, the interpretation of which can vary with the particular property.

    So what does the value of the font property represent in these cases?

It represents an ATOM for a string value.

    What does it represent in general, when the original BDF font
    description gives something other than a single number value to a font
    property?

BDF basically provides for numbers and strings.