Xref: utzoo comp.windows.x:19584 comp.fonts:1091
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uwm.edu!rpi!zaphod.mps.ohio-state.edu!usc!ucla-cs!penzance!tek
From: tek@penzance.cs.ucla.edu (Ted Kim (Random Dude))
Newsgroups: comp.windows.x,comp.fonts
Subject: Re: OpenFonts under X11
Message-ID: <32751@shemp.CS.UCLA.EDU>
Date: 9 Mar 90 20:55:41 GMT
References: <132747@sun.Eng.Sun.COM>
Sender: news@CS.UCLA.EDU
Reply-To: tek@cs.ucla.edu (Ted Kim (Random Dude))
Organization: UCLA
Lines: 29

In article <132747@sun.Eng.Sun.COM> elric@imryrr.Sun.COM (Rick Heli) writes:
>Here's some information on how you can use the recently announced F3
>format OpenFonts with the MIT sample server:
>
> [ how to do it deleted ]

It should be noted though, the following limitations exist with the
X11 fonts generated by this procedure:

1. The XLFD attributes are not generated in this process. So you end
   up with fonts called "Helvitica-8" not 
   "-adobe-helvetica-medium-r-normal--8-80-75-75-p-46-iso8859-1"

2. None of the font properties (eg QUAD_WIDTH) are generated.

3. The fonts all come out as if designed for 72 dpi. (not 75 dpi or
   100 dpi) 

4. The Symbol and Zapf Dingbats fonts require special handling, due to
   their use of a special character encoding.

Anyone know how to overcome these limitations?

-ted

Ted Kim                           
UCLA Computer Science Department  Internet: tek@penzance.cs.ucla.edu
3804C Boelter Hall                UUCP:    ...!{uunet|ucbvax}!cs.ucla.edu!tek
Los Angeles, CA 90024		  Phone:   (213) 206-8696