MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2ED41.289F9780"
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>
Content-class: urn:content-classes:message
Subject:      Re: xhead - a template pretending to be like fancyhdr
Date: Tue, 18 Mar 2003 12:20:28 +0100
Message-ID: A<15991.252.381939.481484@istrati.mittelbach-online.de>
Thread-Topic:      Re: xhead - a template pretending to be like fancyhdr
Thread-Index: AcLtQSlZdtZBqv5RQi6Den6gnvU/Iw==
From: "Frank Mittelbach" <frank.mittelbach@LATEX-PROJECT.ORG>
To: <LATEX-L@listserv.uni-heidelberg.de>
Reply-To: "Mailing list for the LaTeX3 project" <LATEX-L@listserv.uni-heidelberg.de>
Status: R

This is a multi-part message in MIME format.

------_=_NextPart_001_01C2ED41.289F9780
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Achim Blumensath writes:

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

adding Peter's contribution was not meant as a value statement one way =
or the
other. so if you dig up your attempt i'll put it side-long (or anything =
else
for that matter as long as it is documented and helps in thinking =
further
about these matters)

what the disucssion so far tells me (though that isn't really surprising =
:-)
is that what is really missing is thinking further about the interfaces
itself, e.g.

  - what kind of template-type (s) is wanted, what exactly should it do?
  - what are the explicit/implicit inputs?

frank

------_=_NextPart_001_01C2ED41.289F9780
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>     Re: xhead - a template pretending to be like =
fancyhdr</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Achim Blumensath writes:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&gt; use four instances, one for each of these =
cases? That's the approach my</FONT>

<BR><FONT SIZE=3D2>&nbsp;&gt; one head-package used (which never made it =
to the experimental</FONT>

<BR><FONT SIZE=3D2>&nbsp;&gt; directory, but it should be somewhere in =
the mailing list archives).</FONT>
</P>

<P><FONT SIZE=3D2>adding Peter's contribution was not meant as a value =
statement one way or the</FONT>

<BR><FONT SIZE=3D2>other. so if you dig up your attempt i'll put it =
side-long (or anything else</FONT>

<BR><FONT SIZE=3D2>for that matter as long as it is documented and helps =
in thinking further</FONT>

<BR><FONT SIZE=3D2>about these matters)</FONT>
</P>

<P><FONT SIZE=3D2>what the disucssion so far tells me (though that isn't =
really surprising :-)</FONT>

<BR><FONT SIZE=3D2>is that what is really missing is thinking further =
about the interfaces</FONT>

<BR><FONT SIZE=3D2>itself, e.g.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp; - what kind of template-type (s) is wanted, =
what exactly should it do?</FONT>

<BR><FONT SIZE=3D2>&nbsp; - what are the explicit/implicit =
inputs?</FONT>
</P>

<P><FONT SIZE=3D2>frank</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2ED41.289F9780--