Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 17 Mar 2003 18:28:41 +0100 Received: by mail.proteosys.com (8.12.3/8.12.2) with ESMTP id h2HHSca9010243 for ; Mon, 17 Mar 2003 18:28:39 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.8/8.12.8) with ESMTP id h2HHLile021363; Mon, 17 Mar 2003 18:21:44 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2ECAA.A6FD2A80" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h2H6Sbx7020163; Mon, 17 Mar 2003 18:20:53 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 10602 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 17 Mar 2003 18:20:51 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h2HHKoh1025305 for ; Mon, 17 Mar 2003 18:20:50 +0100 Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by relay.uni-heidelberg.de (8.12.8/8.12.8) with ESMTP id h2HHLMvW011377 for ; Mon, 17 Mar 2003 18:21:23 +0100 (MET) Received: from blv-av-02.boeing.com ([192.42.227.217]) by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id JAA16097 for ; Mon, 17 Mar 2003 09:21:21 -0800 (PST) Received: from slb-hub-01.boeing.com (localhost [127.0.0.1]) by blv-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id JAA26567 for ; Mon, 17 Mar 2003 09:21:20 -0800 (PST) Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231]) by slb-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h2HHLIM12809 for ; Mon, 17 Mar 2003 09:21:19 -0800 (PST) Received: from XCH-NW-28.nw.nos.boeing.com ([192.48.4.102]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 17 Mar 2003 09:20:32 -0800 Content-class: urn:content-classes:message Return-Path: X-MimeOLE: Produced By Microsoft Exchange V6.5 X-OriginalArrivalTime: 17 Mar 2003 17:20:32.0894 (UTC) FILETIME=[840E19E0:01C2ECA9] x-mime-autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id h2HHKoh1025306 X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: 1.1 (*) SPAM_PHRASE_03_05,SUPERLONG_LINE Subject: Re: xhead - a template pretending to be like fancyhdr Date: Mon, 17 Mar 2003 18:20:32 +0100 Message-ID: A<3BFEACE361F5BF429DD1DA593E3A7C0922402C@XCH-NW-28.nw.nos.boeing.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: xhead - a template pretending to be like fancyhdr Thread-Index: AcLsVt9VXBlMbQg1QQmOna93wesRVAATZCBg From: "Wilson, Peter R" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4580 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2ECAA.A6FD2A80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks to Achim and Javier for their comments. Achim: This was my first attempt at doing anything with templates and I was = just happy to get something that seemed to work. If I can't get the = notion of instances into my head I'll ask about them later. Javier: In the standard classes, and the memoir class, the marks do not = naturally include any formatting information --- all that the \chapter, = etc., commands do is make the title available to a \chaptermark, etc., = macro. The pagestyle code defines the \chaptermark and that is where the = formating is specified. There is no reason why the pagestyle mechanism cannot use its = definition of \...mark to store the the number and title as = \chapternumber and \chaptertitle macros. I guess, though, that you are = suggesting that \chapter define these macros instead of letting the page = style code define them if it needs them. If LaTeX3 can support arbitrary areas on the page then your = suggestion of any number/location of head/foot areas is interesting. On = the other hand, the zero-sized picture method seems to provide an = adequate means of putting things at specified positions on the page. Come to think about that, how about only one head area and do = everything else (e.g., n-number of head sub-areas, foot areas, side = areas) via zero-sized pictures? Peter W. ------_=_NextPart_001_01C2ECAA.A6FD2A80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: xhead - a template pretending to be like = fancyhdr

    Thanks to Achim and Javier for = their comments.

Achim:
    This was my first attempt at doing = anything with templates and I was just happy to get something that = seemed to work. If I can't get the notion of instances into my head I'll = ask about them later.

Javier:
    In the standard classes, and the = memoir class, the marks do not naturally include any formatting = information --- all that the \chapter, etc., commands do is make the = title available to a \chaptermark, etc., macro. The pagestyle code = defines the \chaptermark and that is where the formating is = specified.

    There is no reason why the = pagestyle mechanism cannot use its definition of \...mark to store the = the number and title as \chapternumber and \chaptertitle macros. I = guess, though, that you are suggesting that \chapter define these macros = instead of letting the page style code define them if it needs = them.

    If LaTeX3 can support arbitrary = areas on the page then your suggestion of any number/location of = head/foot areas is interesting. On the other hand, the zero-sized = picture method seems to provide an adequate means of putting things at = specified positions on the page.

    Come to think about that, how about = only one head area and do everything else (e.g., n-number of head = sub-areas, foot areas, side areas) via zero-sized pictures?

Peter W.

------_=_NextPart_001_01C2ECAA.A6FD2A80--