Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Mon, 17 Mar 2003 20:13:13 +0100 Received: by mail.proteosys.com (8.12.3/8.12.2) with ESMTP id h2HJD8a9010613 for ; Mon, 17 Mar 2003 20:13:11 +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 h2HJ8Ple015520; Mon, 17 Mar 2003 20:08:26 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2ECB9.41646A80" 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 h2H6Sb1L020163; Mon, 17 Mar 2003 20:07:50 +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 10714 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 17 Mar 2003 20:07:50 +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 h2HJ7oh1026067 for ; Mon, 17 Mar 2003 20:07:50 +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 h2HJ8MvW008313 for ; Mon, 17 Mar 2003 20:08:22 +0100 (MET) Received: from Ordenador-de-Javier-Bezos.local. (62-37-92-137.dialup.uni2.es [62.37.92.137]) by smtp.wanadoo.es (8.12.8/8.12.8) with SMTP id h2HJGEVC013557 for ; Mon, 17 Mar 2003 20:16:15 +0100 In-Reply-To: <3BFEACE361F5BF429DD1DA593E3A7C0922402C@XCH-NW-28.nw.nos.boeing.com> References: <3BFEACE361F5BF429DD1DA593E3A7C0922402C@XCH-NW-28.nw.nos.boeing.com> Return-Path: X-Mailer: GyazMail version 0.9.3 X-OriginalArrivalTime: 17 Mar 2003 19:13:13.0496 (UTC) FILETIME=[41B01980:01C2ECB9] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -1.3 () IN_REP_TO,MAY_BE_FORGED,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_02_03 Content-class: urn:content-classes:message Subject: Re: xhead - a template pretending to be like fancyhdr Date: Mon, 17 Mar 2003 20:10:20 +0100 Message-ID: A<20030317201020549218.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: AcLsuUHTAuUe3xxnQKa67dZPrfJ1WA== From: "Javier Bezos" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4585 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2ECB9.41646A80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Peter: > 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. Then, let's imagine the following: a GUI (Perl/Tk, Python/Tkinter, Java/Swing... what you like) which will allow to draw the areas in the page and define their meanings -- page dependent and "flowing". Unfortunately, flow text areas must have the same width (well, if these areas contain only text one could devise a way to change the width by measuring the remaining space and then applying \parshape if necessary). While still limited (no text wrapping figures), it would make *a lot* easier to design more fancier layouts. Javier ___________________________________________________________ Javier Bezos | TeX y tipografia jbezos at wanadoo dot es | http://perso.wanadoo.es/jbezos/ ........................................................... CervanTeX http://www.cervantex.org ------_=_NextPart_001_01C2ECB9.41646A80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: xhead - a template pretending to be like = fancyhdr

Peter:

>     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.

Then, let's imagine the following: a GUI (Perl/Tk, = Python/Tkinter,
Java/Swing... what you like) which will allow to draw = the areas
in the page and define their meanings -- page = dependent and "flowing".
Unfortunately, flow text areas must have the same = width (well, if these
areas contain only text one could devise a way to = change the width
by measuring the remaining space and then applying = \parshape if
necessary). While still limited (no text wrapping = figures), it would
make *a lot* easier to design more fancier = layouts.

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_01C2ECB9.41646A80--