🚀 go-pugleaf

ronald@lowt.phys.tue.nl (Ronald Aarts) writes:
>bruno@thunder.mcrcim.mcgill.edu (Bruno Hall) writes:
>
>>If memory serves, xdvi-1? (where ? < 4) does not support virtual
>>fonts.  Here I'm running dvips-5474 and xdvi-14, and it works just
>>fine.
>
>I'm using xdvi-15 with a DEFAULT_FONT_PATH that points to both the pk-directory
>and the destination directory of Metafont.
>However, when I try to preview a *dvi file that is produced with times.sty,
>my xdvi tries to instruct Metafont to make fonts like rptmr.240gf by calling
>"MakeTeXPK rptmr 240 300 0+240/300". This fails as Metafont complains that it

That seems wrong.  Why should MetaFont start up?  There's no rptmr.mf
file, and no need for one (or rptmr???.[pk,gf]).  

Locally, I don't have xdvi make the pk files on demand -- only dvips
(the reason being that I prefer to put all the time-consuming jobs
together).  

>can't find find file `rptmr' and xdvi decides:
>"Can't find font rptmr; using cmr10 instead at 240 dpi"

That makes sense to me :-).  rptmr is in the printer, which explains
why xdvi can't find it.  From the xdvi manual:

	Virtual fonts are also supported,  although  xdvi  does  not
	have any built-in fonts to which they can refer.

What I find strange is that regardless of the setting of the
environment variable XDVIVFS, I still get this last warning.

>This is just an example. There are more error messages like this. 
>So what is wrong ???

Maybe the criteria which xdvi uses to decide when to call MakeTeXPK
are improperly tuned.

>Ronald Aarts

Bruno
-- 
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Bruno Hall  |  VE2HUM  |  bruno@mcrcim.mcgill.edu         
McGill Research Centre for Intelligent Machines - Controls Group
New systems generate new problems -- Join the Flat Earth Society.