X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["675" "Fri" "20" "June" "1997" "16:23:53" "+0100" "Sebastian Rahtz" "s.rahtz@ELSEVIER.CO.UK" nil "25" "Re: discussing relation of LaTeX to TeX successors" "^Date:" nil nil "6" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.5/8.8.4) with ESMTP id RAA02526; Fri, 20 Jun 1997 17:24:32 +0200 (MET DST) Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.3D05A34B@listserv.gmd.de>; Fri, 20 Jun 1997 17:24:14 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 156831 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 20 Jun 1997 17:24:01 +0200 Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by relay.urz.uni-heidelberg.de (8.7.6/8.7.4) with ESMTP id RAA13452 for ; Fri, 20 Jun 1997 17:23:51 +0200 (MET DST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by pillar.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id QAA16498 for ; Fri, 20 Jun 1997 16:19:54 +0100 (BST) Received: from cadair.elsevier.co.uk by snowdon.elsevier.co.uk with SMTP (PP); Fri, 20 Jun 1997 16:24:05 +0100 Received: from knott.elsevier.co.uk (knott.elsevier.co.uk [193.131.197.165]) by cadair.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id QAA03172 for ; Fri, 20 Jun 1997 16:23:58 +0100 (BST) Received: (from srahtz@localhost) by knott.elsevier.co.uk (8.8.3/8.8.5) id QAA21159; Fri, 20 Jun 1997 16:23:53 +0100 (BST) References: <970620155703.ce5a@vms.rhbnc.ac.uk> Message-ID: <199706201523.QAA21159@knott.elsevier.co.uk> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <970620155703.ce5a@vms.rhbnc.ac.uk> Date: Fri, 20 Jun 1997 16:23:53 +0100 From: Sebastian Rahtz Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: discussing relation of LaTeX to TeX successors Status: R X-Status: X-Keywords: X-UID: 2141 Philip Taylor writes: > If there are only TFM files in the tree, then VMS will be as efficient > as any other system in locating a particular file; if the tree has it depends how well it caches, actually. does the search speed up after one traversal? > this area for which I was seeking clarification: is TDS defined in > such a way that there is a TFM tree, a TEX/LaTeX tree, and so on, um, have you _read_ your copy of the TDS? yes, the tds says you will see fonts/tfm/// tex/// seems straightforward enough where there is a problem is if you search tex/.... instead of tex//... possibly. sebastian