Path: utzoo!attcan!uunet!tdatirv!sarima
From: sarima@tdatirv.UUCP (Stanley Friesen)
Newsgroups: comp.windows.x
Subject: Re: OW 2.0, Fonts, and xtex
Keywords: xnews, fonts
Message-ID: <43@tdatirv.UUCP>
Date: 25 Oct 90 23:06:20 GMT
References: <10200@ubc-cs.UUCP> <1990Oct24.182743.8378@agate.berkeley.edu>
Reply-To: sarima@tdatirv.UUCP (Stanley Friesen)
Organization: Teradata Corp., Irvine
Lines: 23

In article <1990Oct24.182743.8378@agate.berkeley.edu> stolcke@ICSI.Berkeley.EDU (Andreas Stolcke) writes:

>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?

Yes, and it is really quite simple, but it makes using a shell script to
automate it rather difficult.  Just use the '-n fontname' option to
convertfont to give the *same* name to each member of a single font family.
This will indicate to bldfont that they belong together.
[Without the -n option convertfont uses the file name as the font name, and
thus includes the point size in the font name, making them seperate families]

The problem is in getting a shell script to recognize a set of files as
comprising a font family and apply the same name to them all.  (Also,
how do you get the script to determine the correct name).

Bye.
Good luck.
-- 
---------------
uunet!tdatirv!sarima				(Stanley Friesen)