Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f81BnZ909244 for ; Sat, 1 Sep 2001 13:49:35 +0200 Received: by webgate.proteosys.de (8.11.4/8.11.0) with ESMTP id f81BnXT28558 . for ; Sat, 1 Sep 2001 13:49:34 +0200 MIME-Version: 1.0 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f81BkmG07669 for ; Sat, 1 Sep 2001 13:46:48 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C132DC.2BAC7180" Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id NAA20124 for ; Sat, 1 Sep 2001 13:46:47 +0200 (MEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f81BklG07665 for ; Sat, 1 Sep 2001 13:46:47 +0200 (MET DST) Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f81Bjbb25301; Sat, 1 Sep 2001 13:45:37 +0200 (MET DST) Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id f81Bimo15838; Sat, 1 Sep 2001 13:44:48 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0376 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 1 Sep 2001 13:44:46 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id f81Biko15832 for ; Sat, 1 Sep 2001 13:44:46 +0200 Received: from tninet.se (franklin.tninet.se [195.100.94.106]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f81BjXb25279 for ; Sat, 1 Sep 2001 13:45:33 +0200 (MET DST) Received: from [195.100.226.130] (du130-226.ppp.su-anst.tninet.se [195.100.226.130]) by franklin.tninet.se (BLUETAIL Mail Robustifier 2.2.2) with ESMTP id 849653.344215.999franklin-s2 for ; Sat, 01 Sep 2001 13:36:55 +0200 In-Reply-To: References: Your message of "Fri, 31 Aug 2001 20:39:42 +0200." Return-Path: X-Sender: haberg@pop.matematik.su.se Content-class: urn:content-classes:message Subject: Re: Compiling from several files Date: Sat, 1 Sep 2001 11:50:36 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4166 This is a multi-part message in MIME format. ------_=_NextPart_001_01C132DC.2BAC7180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 22:25 +0100 2001/08/31, Robin Fairbairns wrote: >not for what the faq is talking about. i thought it might provoke >some lateral thought on your part, but plainly i was fantasising. > >you seemed to want something you could use now, so i thought i'ld >offer something to help (since i'd been there myself). sorry to >disappoint... I published the code I use, and it works for me. :-) As for the general problem of compiling from multiple files, the stuff on the URL you gave does give some lateral thought, but it also appears to be hacks trying = to cope with shortcomings in LaTeX: A normal way for compilers is that if one compiles a file, then one gets = an object file associated with its filename, and nothing else. By contrast, \include of LaTeX also writes .aux files for the included files, which = thus are not directly invoked by the compilation command. It means that if = one then compiles subfiles in separate compiles, these will wrote over the object information of the main file. Thus, LaTeX would need to be = changed to only write one .aux file, for this scheme to work. In addition, if one compiles a subfile, and that contains = cross-references to other files, then one would want a scheme to indicate that one wants = to read those .aux files as well. >> Have you decided to keep the preamble style for LaTeX3, or is it not >> possible to remove it? > >i haven't _decided_ anything about latex3. many people have made many >proposals that look pretty good to me. but i have to admit i've yet >to encounter a markup language which does away with any declaration of >details of markup to be used ... it's sort of difficult. It looks to me as though LaTeX3 will need some variation of Omega. Then = one might need to have a look if TeX should be tweaked so that one can do = away with the preamble style somehow, that is, instead of having global declarations, making them local to a TeX environment. Hans Aberg ------_=_NextPart_001_01C132DC.2BAC7180 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Compiling from several files

At 22:25 +0100 2001/08/31, Robin Fairbairns = wrote:
>not for what the faq is talking about.  i = thought it might provoke
>some lateral thought on your part, but plainly i = was fantasising.
>
>you seemed to want something you could use now, = so i thought i'ld
>offer something to help (since i'd been there = myself).  sorry to
>disappoint...

I published the code I use, and it works for me. :-) = As for the general
problem of compiling from multiple files, the stuff = on the URL you gave
does give some lateral thought, but it also appears = to be hacks trying to
cope with shortcomings in LaTeX:

A normal way for compilers is that if one compiles a = file, then one gets an
object file associated with its filename, and nothing = else. By contrast,
\include of LaTeX also writes .aux files for the = included files, which thus
are not directly invoked by the compilation command. = It means that if one
then compiles subfiles in separate compiles, these = will wrote over the
object information of the main file. Thus, LaTeX = would need to be changed
to only write one .aux file, for this scheme to = work.

In addition, if one compiles a subfile, and that = contains cross-references
to other files, then one would want a scheme to = indicate that one wants to
read those .aux files as well.

>> Have you decided to keep the preamble style = for LaTeX3, or is it not
>> possible to remove it?
>
>i haven't _decided_ anything about latex3.  = many people have made many
>proposals that look pretty good to me.  but = i have to admit i've yet
>to encounter a markup language which does away = with any declaration of
>details of markup to be used ... it's sort of = difficult.

It looks to me as though LaTeX3 will need some = variation of Omega. Then one
might need to have a look if TeX should be tweaked so = that one can do away
with the preamble style somehow, that is, instead of = having global
declarations, making them local to a TeX = environment.

  Hans Aberg

------_=_NextPart_001_01C132DC.2BAC7180--