X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1178" "Tue" "7" "October" "1997" "13:52:16" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "31" "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 NAA02362; Tue, 7 Oct 1997 13:58:45 +0200 (MET DST) Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <12.8BCDEBA2@listserv.gmd.de>; Tue, 7 Oct 1997 13:58:26 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 209738 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 7 Oct 1997 13:58:17 +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 NAA14783 for ; Tue, 7 Oct 1997 13:58:16 +0200 (MET DST) Received: from [130.237.37.152] (sl06.modempool.kth.se [130.237.37.26]) by mail.nada.kth.se (8.8.7/8.8.4) with ESMTP id NAA06458; Tue, 7 Oct 1997 13:58:15 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199710061037.MAA00326@murnau.idris.fr> Date: Tue, 7 Oct 1997 13:52:16 +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: 2376 At 12:37 +0200 97/10/06, Bernard GAULLE wrote: >..So, may be, >the document hierarchy should not exactly be seen as suggested but >preferably like this: > >\documentclass{MyJournal} >\usepackage[WithToc,WithoutIndex,% some global options of interest > DeferedBiblio,EvenStartingPage]{mmarticle} > \begin{document} > > \begin{mmarticle} > \documentclass{article} % Start of article 1 class > \begin{document} > %% Article 1 stuff > \end{document} % End of article 1 class > \end{mmarticle} Well, the idea is that the different document hierarchy entities involved should be able to program whatever they want, plus being able to handshake the information they need to exchange. (I just did not go into the details.) So sure, a journal option should be able to tell if it is supposed to override the corresponding article option, or if it is supposed take effect only if the article does not override it. Hans Aberg * AMS member: Listing * Email: Hans Aberg * Home Page: