X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["944" "Mon" "23" "December" "1996" "20:10:35" "+0100" "Frank Mittelbach" "Frank.Mittelbach@uni-mainz.de" nil "23" "Re: Multiple pass LaTeX3" "^Date:" nil nil "12" nil "Multiple pass LaTeX3" nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.4/8.8.4) with ESMTP id UAA16467 for ; Mon, 23 Dec 1996 20:35:03 +0100 (MET) Received: from listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <10.3D030D99@listserv.gmd.de>; Mon, 23 Dec 1996 20:35:03 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 9949 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 23 Dec 1996 20:34:55 +0100 Received: from kralle.zdv.Uni-Mainz.DE (kralle.zdv.Uni-Mainz.DE [134.93.8.158]) by relay.urz.uni-heidelberg.de (8.7.6/8.7.4) with ESMTP id UAA06202 for ; Mon, 23 Dec 1996 20:34:54 +0100 (MET) Received: from frank.zdv.uni-mainz.de (Ufrank@localhost) by kralle.zdv.Uni-Mainz.DE (8.8.4/8.8.4) with UUCP id UAA04164 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 23 Dec 1996 20:32:56 +0100 (MET) X-Authentication-Warning: kralle.zdv.Uni-Mainz.DE: Ufrank set sender to frank.zdv.uni-mainz.de!latex3 using -f Received: (from latex3@localhost) by frank.zdv.uni-mainz.de (8.6.9/8.6.9) id UAA16786; Mon, 23 Dec 1996 20:10:35 +0100 References: Message-ID: <199612231910.UAA16786@frank.zdv.uni-mainz.de> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Date: Mon, 23 Dec 1996 20:10:35 +0100 From: Frank Mittelbach Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Multiple pass LaTeX3 Status: R X-Status: X-Keywords: X-UID: 1782 Hans Aberg writes: > Even though TeX is a single pass compiler, multiple passes can be made by > reading a file several times. > > So I suggest one might consider adding this as a feature of LaTeX3: > > For example, if one wants to automate the LaTeX standard two-pass > compile, the environment "document" data would be put in a special file, > which is read twice; if this feature is chosen, the first pass could then > be done without actual typesetting, making it faster. i fear that i don't understand what you mean. what "data" can be put into a special file? most of the reason why you need the typesetting several times (and it might be even more than two) is to gather information from the visual context of the document, eg \pageref can only report the correct number if everything up to that point is already correctly typeset. can you explain a little bit what you have in mind? and merry Xmas to everybody frank