Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 10 Nov 2009 11:35:41 +0100 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id nAAAZe7Q005920 for ; Tue, 10 Nov 2009 11:35:40 +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 nAAAWZ5U005266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Nov 2009 11:32:35 +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 nAA9E8aQ021466; Tue, 10 Nov 2009 11:32:33 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 371465 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 10 Nov 2009 11:32:33 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id nAAAWXgj016698 for ; Tue, 10 Nov 2009 11:32:33 +0100 Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.210.172]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id nAAAWSTU005196 for ; Tue, 10 Nov 2009 11:32:32 +0100 Received: by yxe2 with SMTP id 2so3296611yxe.18 for ; Tue, 10 Nov 2009 02:32:28 -0800 (PST) Received: by 10.150.107.4 with SMTP id f4mr15502150ybc.286.1257849138473; Tue, 10 Nov 2009 02:32:18 -0800 (PST) Received: from ?10.0.1.103? (114-30-99-50.ip.adam.com.au [114.30.99.50]) by mx.google.com with ESMTPS id 20sm241227ywh.47.2009.11.10.02.32.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 10 Nov 2009 02:32:17 -0800 (PST) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) References: <19189.17593.814557.704925@morse.mittelbach-online.de> <4AF5A79B.9040003@residenset.net> <19189.49743.74826.581704@morse.mittelbach-online.de> <004001ca6051$e9e35e10$bdaa1a30$@de> <19192.38156.431785.622764@morse.mittelbach-online.de> <002101ca61d4$f322ddf0$d96899d0$@de> X-Mailer: Apple Mail (2.936) X-Spam-Whitelist: Message-ID: <20C53106-7650-4EAC-82C1-BEF0EFA17816@gmail.com> Date: Tue, 10 Nov 2009 21:02:11 +1030 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Will Robertson Subject: Re: an object type for heading commands To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <002101ca61d4$f322ddf0$d96899d0$@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: 10 Nov 2009 10:35:41.0139 (UTC) FILETIME=[8CD6F230:01CA61F1] Status: R X-Status: X-Keywords: X-UID: 6154 On 10/11/2009, at 5:40 PM, Ulrich Dirr wrote: > I don't know if I understand everything and how powerful and > flexible the > new concept will be. At the level that Frank is taking about, he's discussing what different sorts of information can be used to format an arbitrary section heading. But the important thing to remember is that this is not the user interface. The idea of an "object type" in xtemplate refers only to the information given to it, not how that information eventually ends up in the typeset document. > My concern was that if putting all in one 'heading' command in some > cases it > will get overloaded and unreadable ... Don't worry, this can all be handled by optional/keyval arguments at the document level. But it's important to design the "heading" object sufficiently generally that it can handle most sensible document designs. In my head I imagine something like \section{Main Title That is Very Long and Involves Lots of Things} [ label = main-title , toc-entry = Main Title That is Very Long , header-entry = Main Title , numbered = false ] or something like that. Internally, this might end up as the equivalent of \TheTemplateThatProcessesUnnumberedSections {Main Title That is Very Long and Involves Lots of Things} {main-title} {Main Title That is Very Long} {Main Title} {}{}{}% <- depending on any extra arguments for author info, etc. but because it's all internal (and obviously that control sequence is fictitious) the actual arrangements of the arguments aren't important. > Is it possible to attach files? Anyway I give it a try and attach a > sample > of two pages of the book toc I've been talking above. Nice example, thanks. -- Will