[4401] in testers

home help back first fref pref prev next nref lref last post

Re: potential bug in dvips on 8.4

daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue May 30 09:59:56 2000

Message-Id: <200005301359.JAA15704@small-gods.mit.edu>
To: Liana Lareau <fyfer@MIT.EDU>
Cc: testers@MIT.EDU
In-Reply-To: Your message of "Sun, 28 May 2000 22:19:31 EDT."
             <200005290219.WAA03758@x15-cruise-basselope.mit.edu> 
Date: Tue, 30 May 2000 09:59:50 -0400
From: Greg Hudson <ghudson@MIT.EDU>

> dvips on x15-cruise-basselope, one of SIPB's 8.4 beta machines,
> seems to need to build all the fonts the first time it is run on a
> given dvi file.

Thanks for reporting this.  It never occurred to me that tetex could
ship with such a giant data file and not actually have any compiled
fonts.  I'm glad to see that the automatic font generation stuff works
well, at least.  (I'm confident that the /afs/dev.mit.edu/... paths,
while alarming, are simply a result of path canonicalization.  On
Linux machines, where /usr/athena lives on local disk, the paths show
up starting with /usr/athena.)

I have looked over the tetex install documentation and believe it
shouldn't be too hard to generate a reasonable set of compiled fonts
at install time.  So I'll attempt to do that.

home help back first fref pref prev next nref lref last post