Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!wuarchive!uunet!mcsun!ukc!strath-cs!str-va!cnbr17
From: cnbr17@vaxa.strath.ac.uk
Newsgroups: comp.windows.x
Subject: Re: Running Open Look apps using other than OLWM
Message-ID: <1991Jun13.110743.11860@vaxa.strath.ac.uk>
Date: 13 Jun 91 11:07:43 GMT
References: <99199@lll-winken.LLNL.GOV> <1991Jun12.003134.19814@eng.umd.edu>
Organization: University of Strathclyde, Elec. Eng.
Lines: 50

In article <1991Jun12.003134.19814@eng.umd.edu>, stripes@eng.umd.edu (Joshua Osborne) writes:
> In article <99199@lll-winken.LLNL.GOV> guerra@cae.llnl.gov (Frank M. Guerra) writes:
>>I've been waiting for someone to beg the question on why running an Open Look
>>application under twm, or anything but olwm fails.  It always complains about 
>>certain fonts not being found.  Okay, so someone figures that the .ff fonts in
>>/usr/openwin/lib/fonts need to be converted to .snf in order to be recognized.
>>Well, apparently, that's not quite it either.  So, is there any workarounds, or
>>is this just the way it is?  I know that certain things like pushpins go away, but
>>I would expect that.  Insights anyone?

Hi,
I don't know much about using other window managers, but I suspect the
problem with the fonts is due to you running under X rather than Xnews.

I run a lot of OpenLook applications under vanilla X -- cmdtools, filemgr,
mailtool and the calendar manager being the main ones. I had to mess about
with the fonts to get them to work properly -- particularly for cm. Here's
what I did:

1. Use convertfont to dump all of the OW fonts as BDF fonts.

2. Use bdftosnf to get the SNF fonts

3. Use mkfontdir to create fonts.dir in the new font directory.

4. Add the following lines to fonts.alias (in our case this was in
/usr/lib/X11/fonts/misc):

   screen.r.9   -b&h-lucida-medium-r-normal-sans-*-120-**-*-*-*-*
   Helvetica    helvetica-12
   -b&h-lucida-medium-r-normal-sans-9-90-75-75-p-58-iso8859-1 lucidasans-10
   -b&h-lucida-bold-r-normal-sans-9-90-75-75-p-58-iso8859-1 lucidasans-bold-10

Figuring out which aliases to use for the last part was the most difficult.
Basically I had to look at the error messages I was getting (ie which fonts
the server couldn't find), then look at the files Synonyms.list and
Compat.list in $OPENWINHOME/lib/fonts to find out the full names of those
fonts, and then add the appropriate aliases.

Hope this is of use to you,
Peter.

-- 
================================================================================
Peter Duffy           |JANET:   p.duffy@uk.ac.strath.vaxa
EEE Dept.             |Internet:p.duffy%vaxa.strath.ac.uk@nsfnet-relay.ac.uk
Strathclyde University|BITNET:  p.duffy%vaxa.strath.ac.uk@UKACRL
Glasgow G1 1XW        |UUCP:    p.duffy%vaxa.strath.ac.uk@ukc.uucp
Scotland.             |
================================================================================