🚀 go-pugleaf

In article <570016@otter.hpl.hp.com> gjh@otter.hpl.hp.com (Graham Higgins) writes:
>I have found that my version (3.3) of dvist tells pork pies (lies) when
>reporting an unsuccessful font search - it reports "unable to open 
>cmbx10/96pk" when it *really* means that it can't find cmbx10/105pk
>       ^^                                                     ^^^      

	No, its not telling any lies, it really cannot find that 
file.  The dvi font loader attempts to find a font +/- 9 from the
calculated magnification to overcome missing fonts and more importantly
round-off errors that we had encountered.

>	One of the problems I've encountered is that it seems
> to lose track of what font it's supposed to be getting characters
> out of.  I tried running a font table (as produced by testfont.tex)
> for cmr10 out to the laser printer with dvihp.  It used the correct
> font for some of the time, the wrong font elsewhere.  Some characters
> were lost completely.

	This is a new one that we will attempt to look into.  Did the
program work properly with the given dvi file.  We have used this 
program extensively on UNIX, OS/9 and to a far more limited extent,
TOS and haven't encounted this problem.  We will try out dvihp with
the testfont file in the near future.

>	cannot open |f:\fonts\cmr10\201pk'

	Don't worry about the vertical bar.  Those who have programmed
AES will understand it's purpose (i.e. generate a new line in an alert
box) and this has infiltrated itself into all of our program as we
use a common driver for all devices.

	In general, we use any 300dpi pk font for virtually any
laser printer out there.  However, the font quality varies for one
engine to another.  Some devices prefer darker fonts, others lighter
ones to acheive the same density.