🚀 go-pugleaf

In article <32751@shemp.CS.UCLA.EDU> tek@cs.ucla.edu (Ted Kim (Random Dude)) writes:
>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:

Thanks for bringing up some of the nitty-gritty details of this process.
I can offer some, if not complete, assistance.

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

The XLFD names for those fonts supplied with OpenWindows can be found
in $OPENWINHOME/etc/NeWS/fontsyns.ps (you'll need to set pixel size, point
size, resolution and maximum width).  The names would then need to be
changed in the .bdf files (by changing the "FONT" line) or by creation
of a fonts.alias file in the directory holding the fonts.  This file
would contain a line with the short name and XLFD name for each font, e. g.:

Helvetica-8 -adobe-helvetica-medium-r-normal--8-80-75-75-p-46-iso8859-1

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

These properties are not part of OpenFonts and, if desired, would
need to be added by hand.

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

Allowing makeafb to take a dpi argument is under consideration for a
future release.  Unfortunately, it does not permit this at present.

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

I can send the appropriate encoding files for these fonts for anyone who
is interested (send mail) or if I get enough interest, simply post them
to the net.


						Rick Heli
						Internet:  rheli@sun.COM
						UUCP:      ...!sun!rheli