Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Sat, 7 Nov 2009 18:02:50 +0100 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id nA7H2ojM017386 for ; Sat, 7 Nov 2009 18:02:50 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id nA7GwhJH004882 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 7 Nov 2009 17:58:43 +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 nA79mjJB002519; Sat, 7 Nov 2009 17:58:42 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 354909 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 7 Nov 2009 17:58:41 +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 nA7Gwfua021411 for ; Sat, 7 Nov 2009 17:58:41 +0100 Received: from csep02.cliche.se (csep02.cliche.se [195.249.40.184]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id nA7GwQ6G024287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 7 Nov 2009 17:58:29 +0100 Received: from hexley.local (unknown [213.21.117.168]) by csep02.cliche.se (Postfix) with ESMTP id 9534B1865F3 for ; Sat, 7 Nov 2009 17:57:38 +0100 (CET) User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 References: <19189.17593.814557.704925@morse.mittelbach-online.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id nA7Gwfua021412 Message-ID: <4AF5A79B.9040003@residenset.net> Date: Sat, 7 Nov 2009 18:00:11 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: =?ISO-8859-1?Q?Lars_Hellstr=F6m?= 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: 07 Nov 2009 17:02:50.0391 (UTC) FILETIME=[23504270:01CA5FCC] Status: R X-Status: X-Keywords: X-UID: 6136 Frank Mittelbach skrev: > 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. > > 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 ...) That one feels a bit wobbly. But is your thinking that this kind of information is frequently appearing in page heads, and page head contents are being set by this kind of command, so there needs to be a way to pass the information? > - motto/quote text to display alongside the heading title > - flag to number heading Or should numbered and unnumbered headings be generated by separate instances? Needs to be thought about. One additional item could be an external identifier to use for this heading of this document, i.e., the thing that would come after # in an URL. > 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? Isn't that explicit in the above? Or did you rather think about the document-level commands here? > what else is missing or which of the above aren't sensible in the first place? One might consider making one argument a keyval dictionary and collect many of the above in that instead. This would provide for instances behaving as follows: When needing a title for the TOC: 1. If there is a key "toctitle", then use that value. 2. Otherwise, if there is a key "shorttitle", then use that value. 3. Otherwise, use the full title. When needing a title for the running head: 1. If there is a key "headtitle", then use that value. 2. Otherwise, if there is a key "shorttitle", then use that value. 3. Otherwise, use the full title. That way, the optional argument of the 2e \section could be passed to such an instance as a "shorttitle", whereas a more powerful sectioning command could provide for setting "toctitle" and "headtitle" separately. Lars Hellström