Path: utzoo!attcan!uunet!husc6!bbn!mit-eddie!bloom-beacon!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: upper case fontnames
Message-ID: <19880517121134.1.RWS@KILLINGTON.LCS.MIT.EDU>
Date: 17 May 88 12:11:00 GMT
References: <8805162130.AA14397@godzilla.ele.toronto.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 17


    Date: Mon, 16 May 88 17:30:08 EDT
    From: Mark Moraes <moraes%godzilla.ele.toronto.edu@relay.cs.net>

    Just curious - why are all fontnames converted to lowercase by the 
    servers?

To obey the protocol spec.

    The server documents mention in passing (where they describe
    ExpandFontName, I think) that the fontnames should be
    case-insensitive. Shouldn't that match both lower and upper case?

The current (undocumented, of course) implementation restriction in the
Unix OS layer is that fonts must be stored using lowercase filenames.
(This is arguably an undesirable restriction.)  Font names coming in
over the protocol are thus converted to lowercase for correct matching.