Path: utzoo!attcan!uunet!samsung!sol.ctr.columbia.edu!lll-winken!unixhub!shelby!agate!ICSI.Berkeley.EDU!stolcke
From: stolcke@ICSI.Berkeley.EDU (Andreas Stolcke)
Newsgroups: comp.windows.x
Subject: Re: OW 2.0, Fonts, and xtex
Keywords: xnews, fonts
Message-ID: <1990Oct24.182743.8378@agate.berkeley.edu>
Date: 24 Oct 90 18:27:43 GMT
References: <10200@ubc-cs.UUCP>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: stolcke@ICSI.Berkeley.EDU (Andreas Stolcke)
Organization: International Computer Science Institute, Berkeley, CA
Lines: 32

In article <10200@ubc-cs.UUCP>, hook@cheddar.ucs.ubc.ca (Chris Hook) writes:
|> 
|> My problem: When I'm in openwin (2.0), niether I nor any of my users
|> can properly read the fonts for xtex. (paths are all set using xset +fp)
|> Now, if one starts up X11R4, then all fonts are found, and there is no problem.
|> Is there something peculiar to xtex that I need to be aware of?

Xnews uses a different font format, so you have to recompile all your TeX
fonts dpecifically for xnews.  Assuming you have the collection of bdf.Z files from foobar.colorado.edu, you can run the following script to do the job:

#!/bin/sh
tmp=/tmp/temp.bdf
for font in *bdf.Z ;
do
  base=`echo $font | sed -e 's/\.bdf\.Z//'`
  zcat $font >$tmp
  convertfont -d . -o $base $tmp
done
bldfamily -f 128 -d .

Then copy all the *.ff, *.fb and *.list files into some font directory
and make it accessible to the  xnews server (using xset fp+).

Be warned however: Since Xnews doesn't seem to handle compressed font files,
the whole collection uses about 7MB of disk space.  Also, bldfamily 
doesn't recognize same fonts at different resolutions and styles as belonging to one font family and creates .ff files for every single .fb file. 
Anybody have a fix for that?

-- 
Andreas Stolcke
International Computer Science Institute	stolcke@icsi.Berkeley.EDU
1957 Center St., Suite 600, Berkeley, CA 94704	(415) 642-4274 ext. 126