Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 17 Mar 2003 11:16:37 +0100 Received: by mail.proteosys.com (8.12.3/8.12.2) with ESMTP id h2HAGYa9008878 for ; Mon, 17 Mar 2003 11:16:35 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.8/8.12.8) with ESMTP id h2HACMvW000669; Mon, 17 Mar 2003 11:12:22 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2EC6E.4B14B080" 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 h2H6Sblb020163; Mon, 17 Mar 2003 11:11:29 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 9986 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 17 Mar 2003 11:11:29 +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 h2HABTh1021613 for ; Mon, 17 Mar 2003 11:11:29 +0100 Received: from smtp.wanadoo.es (smtp4.wanadoo.es [62.37.236.138] (may be forged)) by relay.uni-heidelberg.de (8.12.8/8.12.8) with ESMTP id h2HABrvW000364 for ; Mon, 17 Mar 2003 11:11:53 +0100 (MET) Received: from Ordenador-de-Javier-Bezos.local. (62-37-92-60.dialup.uni2.es [62.37.92.60]) by smtp.wanadoo.es (8.12.8/8.12.8) with SMTP id h2HAJgVC022915 for ; Mon, 17 Mar 2003 11:19:43 +0100 In-Reply-To: <20030317082835.B2130@diabolo.informatik.rwth-aachen.de> References: <3BFEACE361F5BF429DD1DA593E3A7C090131346A@XCH-NW-28.nw.nos.boeing.com> <20030317082835.B2130@diabolo.informatik.rwth-aachen.de> Return-Path: X-Mailer: GyazMail version 0.9.3 X-OriginalArrivalTime: 17 Mar 2003 10:16:37.0497 (UTC) FILETIME=[4B608690:01C2EC6E] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -1.6 () IN_REP_TO,MAY_BE_FORGED,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02 Content-class: urn:content-classes:message Subject: Re: xhead - a template pretending to be like fancyhdr Date: Mon, 17 Mar 2003 11:12:51 +0100 Message-ID: A<20030317111251158860.GyazMail.jbezos@wanadoo.es> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: xhead - a template pretending to be like fancyhdr Thread-Index: AcLsbkt5mW+Taw3ATuK3BdTUaZurPA== From: "Javier Bezos" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4579 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2EC6E.4B14B080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > Hello, > > On Fri, Mar 14, 2003 at 10:50:02AM -0800, Wilson, Peter R wrote: >> I had a go at such a beast (called xhead) about a year ago. >> I'll be interested in any comments about it; be gentle, though, as >> it's my first attempt. > > Why did you chose to have one template containing all four > head-/footlines (even/odd head/foot)? Wouldn't it be simpler to = instead > use four instances, one for each of these cases? That's the approach = my > one head-package used (which never made it to the experimental > directory, but it should be somewhere in the mailing list archives). Actually, I think LaTeX running heads have a serious design flaw: the two-step mechanism and the fact \bot/top/firstmarks contain formatted information (ie, number and title are already gathered and with \MakeUppercase). IMO, the mechanism of the current \chapter/sectionmarks should be hidden to the user (at least in most of cases), and the chapter/section/etc titles and numbers should be made available as macros named, say, \chaptertitle, \chapternumber, etc., directly available in the place where running heads are defined. (If you have used my titlesec package, you will understand what I mean). Another useful addition would be the possibility to define arbitrary head/foot areas (not only a top or and a bottom line) where this information could be placed. For example: the chapter title could go in the headline and the chapter number at the outer margin (vertically centered) in a shaded box. (Well, the code of titlesec has a hook for that, but I've never implemeted it...). Javier ___________________________________________________________ Javier Bezos | TeX y tipografia jbezos at wanadoo dot es | http://perso.wanadoo.es/jbezos/ ........................................................... CervanTeX http://www.cervantex.org ------_=_NextPart_001_01C2EC6E.4B14B080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: xhead - a template pretending to be like = fancyhdr

> Hello,
>
> On Fri, Mar 14, 2003 at 10:50:02AM -0800, = Wilson, Peter R wrote:
>> I had a go at such a beast (called xhead) = about a year ago.
>> I'll be interested in any comments about it; = be gentle, though, as
>> it's my first attempt.
>
> Why did you chose to have one template = containing all four
> head-/footlines (even/odd head/foot)? Wouldn't = it be simpler to instead
> use four instances, one for each of these cases? = That's the approach my
> one head-package used (which never made it to = the experimental
> directory, but it should be somewhere in the = mailing list archives).

Actually, I think LaTeX running heads have a serious = design flaw:
the two-step mechanism and the fact = \bot/top/firstmarks contain
formatted information (ie, number and title are = already
gathered and with \MakeUppercase). IMO, the = mechanism
of the current \chapter/sectionmarks should be hidden = to the
user (at least in most of cases), and the = chapter/section/etc
titles and numbers should be made available as macros = named, say,
\chaptertitle, \chapternumber, etc., directly = available in the
place where running heads are defined. (If you have = used my
titlesec package, you will understand what I = mean).

Another useful addition would be the possibility to = define
arbitrary head/foot areas (not only a top or and a = bottom line)
where this information could be placed. For = example:
the chapter title could go in the headline and the = chapter
number at the outer margin (vertically centered) in = a
shaded box. (Well, the code of titlesec has a hook = for
that, but I've never implemeted it...).

Javier
___________________________________________________________
Javier = Bezos           &n= bsp;  | TeX y tipografia
jbezos at wanadoo dot es  | http://perso.wanadoo.es/jbezos/<= /A>
...........................................................
CervanTeX   http://www.cervantex.org

------_=_NextPart_001_01C2EC6E.4B14B080--