From owner-freebsd-ports Mon Apr 10 15:03:59 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10524 for ports-outgoing; Mon, 10 Apr 1995 15:03:59 -0700 Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA10487 for ; Mon, 10 Apr 1995 15:03:32 -0700 Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA17165; Tue, 11 Apr 95 00:01:28 +0100 Date: Tue, 11 Apr 95 00:01:28 +0100 From: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Message-Id: <9504102301.AA17165@cabri.obs-besancon.fr> To: paul@isl.cf.ac.uk Cc: asami@cs.berkeley.edu, vince@kbrown.oldcampus.yale.edu, ports@FreeBSD.org In-Reply-To: <199504101719.SAA25825@isl.cf.ac.uk> (message from Paul Richards on Mon, 10 Apr 1995 18:19:07 +0100 (BST)) Subject: Re: /etc/printcap for Deskjet 500 and gs X-Mailer: Emacs Sender: ports-owner@FreeBSD.org Precedence: bulk >>>>> "Paul" == Paul Richards writes: [...] > Incidentally, since we're talking about TeX and it's friends I have a few > queries. First, what happened to the directory searching functions that > we had in 1.1.5? The kpathsea stuff doesn't seem to search subdirectories > like I thought it should. The latest version of the kpathsearch library has bugs. TeX is of course compiled with the library but the default path has no '//' in it. You can use the directory searching functions if you set the various environment variables (but because of the lib bugs, the path '/usr/local/lib/texmf/fonts//tfm' will not work. However /usr/local/lib/texmf//fonts/tfm will work) This is the main raison for which I have not ported dvipsk and xdvik, and I used the original versions. The directory searching functions are not implemented for dvips and xdvi. > Also, the MakeTeXPK fails under certain circumstances because mf > creates fonts with the name of jobname.gf where depends > on the resolution and magnification of the font. In the MakeTeXPK script, > $GFNAME is set to $NAME.$DPI'gf and $DPI does not alwats map to the > that mf generates, depending on the magnification used. The $DPI variable is provided by xdvi or dvips. Do you mean that the value is incorrectly computed by xdvi or dvips? I have seen rounding errors (eg 745gf instead of 746gf), but only on VMS :-) > The result is that quite often you'll get "Metafont failed for some reason on" > errors because the script is looking for the wrong filename. Does anyone > know how to fix this or who to report it to? > -- > Paul Richards, FreeBSD core team member. > Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ > Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) > Dept. Mechanical Engineering, University of Wales, College Cardiff. Jean-Marc. ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ Jean-Marc Zucconi | jmz@cabri.obs-besancon.fr Observatoire de Besancon | F 25010 Besancon cedex | PGP Key: finger jmz@cabri.obs-besancon.fr =========================================================================