🚀 go-pugleaf

In article <132607@sun.Eng.Sun.COM> hvr@sun.UUCP (Heather Rose) writes:
|All the X11 servers do not use the standard utility bdftosnf to
|compile the font files?  The XView source includes rules for compiling
|the fonts for X11R3 based servers.  


In one case we had a X terminal from company "Q"
This required us to have a machine from that company to compile
the fonts into the right mode. The system that is providing boot
service for our X terminals is an Encore. It's version of native font
formats were not the same as the format neded by that particular terminal.

Also - as I said - I had to FTP the fonts to a Mac and convert them
myself - using a Mac utility. (Finder - not A/UX).

Our world is not heterogenous.
|>The point is - OpenLook fonts are currently non-standard.
|>The mechanism needed to download the fonts are non-standard.
|
|How so?  We provide them in the same format as any other X11 supplied font.
|We provide the same rules for compiling them as any other X11 font.  We also
|add the font to the font database in the same way as any other X11 font.

|OK.  Perhaps what you mean by "non-standard" is that X11 servers that came
|out before X11R4 do not download the OpenLook fonts by default?  That you
|need to run bdftosnf or xset at all...

Yes.

Another question I have - is HP/Apollo, IBM, Apple and DEC going to 
provide OpenLook fonts standard with each of their X servers?

I can believe that a lot of these users might try an XView
application - and get a fatal error because the olcursor font wasn't
there. 


--
-- 
Bruce G. Barnett	barnett@crd.ge.com	uunet!crdgw1!barnett