Date: Sun, 19 Feb 95 13:50:09 -0500 From: crtb@helix.nih.gov (Chuck Bacon) To: bugs@FreeBSD.org Subject: xdvi and latex2e Message-ID: <9502191850.AA08020@helix.nih.gov>
next in thread | raw e-mail | index | archive | help
BUG: latex2e and xdvi both root in /home/jmz/local instead of /usr/local. So I created /home/jmz -> /usr. This apparently worked, although strings xdvi revealed that /home/jmz was needed after installation too. Latex2e apparently works. At least it creates a .dvi file. But both dvips and xdvi either fail or go into a loop trying to find fonts. In particular, xdvi gives a large collection of messages of the form: - MakeTeXPK cmti10 300 300 magstep\(0\) //home/jmz/local/lib/texmf/fonts/pk/cmti10.300pk already exists! - MakeTeXPK cmr10 300 300 magstep\(0\) //home/jmz/local/lib/texmf/fonts/pk/cmr10.300pk already exists! Can't find font cmti10. Similar five-line messages occur for many font names. Always the font name cited for the first MakeTeXPK invocation of a pair is the subject of the "Can't find" message. Of course, I'd rather have 360-dpi fonts, since I have a 360-dpi printer. Should I try to find pre-built fonts from a CTAN archive, or can I trust MakeTeXPK to satisfy my needs? Chuck Bacon - crtb@helix.nih.gov ABHOR SECRECY - DEFEND PRIVACY
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9502191850.AA08020>