X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2190" "Wed" "8" "October" "1997" "14:14:09" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "45" "Re: LaTeX journal and publisher macros" "^Date:" nil nil "10" 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.5) with ESMTP id QAA30552; Wed, 8 Oct 1997 16:46:07 +0200 (MET DST) Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <8.1C49031E@listserv.gmd.de>; Wed, 8 Oct 1997 16:45:55 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 210613 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 8 Oct 1997 16:45:47 +0200 Received: from mail.nada.kth.se (root@mail.nada.kth.se [130.237.222.92]) by relay.urz.uni-heidelberg.de (8.8.7/8.8.7) with ESMTP id QAA23698 for ; Wed, 8 Oct 1997 16:45:32 +0200 (MET DST) Received: from [130.237.37.74] (sl54.modempool.kth.se [130.237.37.74]) by mail.nada.kth.se (8.8.7/8.8.4) with ESMTP id QAA03634 for ; Wed, 8 Oct 1997 16:45:30 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se References: Your message of "Tue, 07 Oct 1997 11:39:12 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199710071753.NAA17629@aleph.swift.xxx> Date: Wed, 8 Oct 1997 14:14:09 +0200 From: Hans Aberg Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: LaTeX journal and publisher macros Status: R X-Status: X-Keywords: X-UID: 2394 Matthew Swift : >There are benefits to the original \include system, but they are not >so great that others should not be considered. The \include system >does not let you do anything you couldn't do with \input. It just >makes it more convenient for long documents. These conveniences don't >seem as wonderful in days of more powerful equipment... This is one aspect that I have in my mind: Computers are getting so fast that making a full compile every once in a while does not hurt. >In fact there are also pitfalls in the old system that it would be >nice to fill in. As I point out in the "review of the old system" >section of the newclude documentation, it is a convenient feature, >when leaving out, say, chapters 2 and 3 from your book that the >references still work, and the footnote numbers and page numbers of >chapter 4 do not change. This allows me to get output of chapters 1 >and 4+ that looks exactly like those sections of the whole document, >without using some sort of post-processor to whittle down the entire >dvi file to the parts I want. I am not sure about the details, but I think one can that with my system: If one has a main file "main.tex", indicated by \project{main} in other files, then a subfile (named "submain.tex") compilation would use two aux files: main.aux and submain.aux. Global (cross file) references would refer to main.aux, and local (file submain.tex) references would refer to submain.aux. So you get the references to work in a way suitable for authoring; if you do a radical change, adding a file, or something, you can always throw in a global compile of main.tex. >But it is a quite unintuitive and inconvenient consequence of the >implementation that that if you switch the order of chapters 2 and 3 >while they are STILL UNINCLUDED, the counters in chapters 4+ are >thrown into chaos. So, I would not bother about this too much, since I would put in a global compile in such a case. Hans Aberg * AMS member: Listing * Email: Hans Aberg * Home Page: