Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Sun, 8 Nov 2009 20:45:49 +0100 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id nA8Jjn8M021885 for ; Sun, 8 Nov 2009 20:45:49 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id nA8JhGEB005973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 Nov 2009 20:43:16 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id nA8DNhtp013298; Sun, 8 Nov 2009 20:43:07 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 353634 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 8 Nov 2009 20:43:07 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id nA8Jh7F1021235 for ; Sun, 8 Nov 2009 20:43:07 +0100 Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id nA8JgtWW005660 for ; Sun, 8 Nov 2009 20:42:59 +0100 Received: from [70.58.84.1] (helo=[192.168.2.3]) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1N7Df4-0005h1-ER; Sun, 08 Nov 2009 14:42:54 -0500 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060212 Fedora/1.7.12-5 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <19189.17593.814557.704925@morse.mittelbach-online.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 2d75d9567fada10dc3b6ad7bd0984c4474bf435c0eb9d478c68cb8952387417ba475dcdc35e3e407672154eff59a0e05350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 70.58.84.1 Message-ID: <4AF6F50E.1080706@earthlink.net> Date: Sun, 8 Nov 2009 11:42:54 -0500 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: peter wilson Subject: Re: an object type for heading commands To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <19189.17593.814557.704925@morse.mittelbach-online.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 08 Nov 2009 19:45:50.0136 (UTC) FILETIME=[12E8AB80:01CA60AC] Status: R X-Status: X-Keywords: X-UID: 6148 Frank Mittelbach wrote: > I do want to try my hand on setting up some templates for headings and for > that the first step is to define a suitable > > \DeclareObjecttype{headings}{?} > > The initial question here is what are the arguments this object type should > carry? for that I hope some of you can help with some thoughts. > > Note that each of the mandatory arguments could well be receiving \NoValue > from the outside and or disregard the argument altogether in most document > classes. So we do have somepossibilities and we need to weight them as whether > something is too esoteric or okay to be made part of the standard even if, > say, it will only get used in 10% of the cases. > > Here is my current list of candiates: > > - title of the heading > - title version to go in the TOC > - title version to go in the running header > - subtitle of the heading (e.g., an author name, copyright notice ...) > - motto/quote text to display alongside the heading title > - flag to number heading > > do we need a way to specify that something is send to the TOC or to the > running header and if so how do we do that? > > what else is missing or which of the above aren't sensible in the first place? > In the memoir class (all LaTeX2e syntax) I have: o Book and Part divisions, plus user commands for creating new part-like title pages. There are hooks for adding book/part titles to running heads. (The Book division was at the request of a French user who needed a level above Part, which I understand to be not atypical in French books). o For \chapter through \subparagraph two optional args for ToC and running header and the mandatory text title. o For \chapter* an optional arg for running head. No number and no ToC entry. o For \section* through \subparagraph* just required arg. No number and no ToC or running head. o A \chapterprecis{} for a synopsis of a chapter which will also go into the ToC. Or you can have a synopsis, just in the text, just in the ToC, or different ones in each. (This has also been used for author information instead). In the ToC a synopsis or author entry needs its own kind of formatting. o An \epigraph{}{} command which can be used anywhere. Typically at the start of a chapter (before or after the title). Remember that the TeXbook has epigraphs at the end of chapters. o Separately, declarations to switch off/on numbering of unstarred \chapter...\subparagraphs. Given the above, which has seemed to cover authors needs, I suggest that any equivalents of \chapterprecis and \epigraph be kept separate from the title and numbering controls for the divisions. They are used rarely and would only clutter a heading specification. BTW I have seen author information placed at the end of a section/chapter rather than with the title. Thinking about author information there could be quite a lot of it: Authors names, affiliations, where and when originally published, permission to reproduce, ... Peter W.