X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1394" "Thu" "28" "October" "1999" "18:28:24" "+0100" "James Kilfiger" "mapdn@CSV.WARWICK.AC.UK" nil "24" "section heading templates" "^Date:" nil nil "10" nil "section heading templates" nil nil nil] nil) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id TAA19143 for ; Thu, 28 Oct 1999 19:30:04 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <1.226434A5@mail.listserv.gmd.de>; Thu, 28 Oct 1999 19:28:54 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 445572 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 28 Oct 1999 19:28:36 +0200 Received: from snowdrop.csv.warwick.ac.uk (snowdrop.csv.warwick.ac.uk [137.205.192.31]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id TAA29117 for ; Thu, 28 Oct 1999 19:28:25 +0200 (MET DST) Received: from mimosa.csv.warwick.ac.uk (mapdn@mimosa [137.205.192.34]) by snowdrop.csv.warwick.ac.uk (8.9.3/8.9.3) with ESMTP id SAA17936 for ; Thu, 28 Oct 1999 18:28:26 +0100 (BST) Received: (from mapdn@localhost) by mimosa.csv.warwick.ac.uk (8.9.3/8.9.3) id SAA15046; Thu, 28 Oct 1999 18:28:24 +0100 (BST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID: <199910281728.SAA15046@mimosa.csv.warwick.ac.uk> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199910011527.LAA04020@hilbert.math.albany.edu> from "William F. Hammond" at "Oct 1, 99 11:27:20 am" Date: Thu, 28 Oct 1999 18:28:24 +0100 From: James Kilfiger Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: section heading templates Status: R X-Status: X-Keywords: X-UID: 3366 I was thinking rather vaguely about templates for sectional heading. I can think of at three style for authors to make sectional headings. As now, with section commands, with section evironments, and in a list-like manner. Templates for headings should be able of supporting classes that use a mixture of these styles. About the syntax for sectional commands, the most useful thing would be a separation of the numbering/nonumbering and table of contents options. A possible approach would be two true/false arguments, would a specification like {s o m s} be hard to remember and use? so perhaps the specification should be something like {s o m o}, the final argument defaulting to [t] for `table of contents' or [ht] for header and table of contents. (BTW this seems to show a general problem in Latex syntax when two or more indepedent optional arguments are required.) It would be useful if the templates allowed putting stuff before or after the section heading, useful for drawing rules and so on. Is this worthy of a an argument to the template. On another matter, how will collection instances be used? Will environments select a collection. Would it be useful if \begin{myenv} implictly called \UseCollection{myenv}. You could use this to prohibit sectional headings in floats, or \item outside of lists. Would this be within the expected use of collections. James