Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Mon, 6 Mar 2000 23:42:55 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id XAA00804 for ; Mon, 6 Mar 2000 23:42:54 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF87BD.4FF9C180" Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id XAA10150 for ; Mon, 6 Mar 2000 23:42:53 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <9.F8AFC6D3@mail.listserv.gmd.de>; Mon, 6 Mar 2000 23:41:34 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 453017 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 6 Mar 2000 23:40:13 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id XAA14974 for ; Mon, 6 Mar 2000 23:40:11 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id XAA21852 for ; Mon, 6 Mar 2000 23:42:49 +0100 Received: from wisbech.cl.cam.ac.uk (mta1.cl.cam.ac.uk [128.232.0.15]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id XAA12891 for ; Mon, 6 Mar 2000 23:40:12 +0100 (MET) Received: from dorceus.cl.cam.ac.uk ([128.232.1.34] helo=cl.cam.ac.uk ident=rf) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 12S6DA-0006Qs-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Mon, 06 Mar 2000 22:42:48 +0000 In-Reply-To: Your message of "Mon, 06 Mar 2000 22:47:47 +0100." <200003062147.WAA01565@kammer.uni-hannover.de> Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1459" "Mon" "6" "March" "2000" "22:42:48" "+0000" "Robin Fairbairns" "Robin.Fairbairns@CL.CAM.AC.UK" nil "34" "Re: bop-hook" "^Date:" nil nil "3" nil "bop-hook" nil nil nil]nil) Content-class: urn:content-classes:message Subject: Re: bop-hook Date: Mon, 6 Mar 2000 23:42:48 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robin Fairbairns" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3544 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF87BD.4FF9C180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable reinhard kotucha writes: > Maybe we have to think about the order the macros are attached to the > hook. but everyone seems to _know_ that a bop-hook function is the thing to do, so surely they've thought about trivia like this already. > If the hook is used by a class and a package, the class would > put the first element to the list and the package the second. The > order is important since that is the order the stuff is printed. Maybe > the templates can help to control the behavior. i continue bemused by this thing. we have (what seems to me) a perfectly adequate mechanism for adding stuff to the printed page, over and above the regular run of document body -- we have the page header and footer mechanisms that the output routine already calls. i don't see what a `printing' bop-hook is going to do that these mechanisms don't already enable. hell, the header/footer mechanisms already _are_ hooks. what we don't have is the means to execute bits of code that directly affect the way the output routine operates. if you want to affect the way footnotes are generated, you have to patch the output routine. there's no existing hook that helps you -- you have to get in there and patch. now, i've no clear model of how we might write an output routine that would facilitate this sort of thing, but it sure as hell isn't by adding bits of code at the start of a page. robin speaking for myself. i don't know what frank's up to either. ------_=_NextPart_001_01BF87BD.4FF9C180 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: bop-hook

reinhard kotucha writes:

> Maybe we have to think about the order the macros = are attached to the
> hook.

but everyone seems to _know_ that a bop-hook function = is the thing to
do, so surely they've thought about trivia like this = already.

> If the hook is used by a class and a package, the = class would
> put the first element to the list and the = package the second.  The
> order is important since that is the order the = stuff is printed. Maybe
> the templates can help to control the = behavior.

i continue bemused by this thing.  we have (what = seems to me) a
perfectly adequate mechanism for adding stuff to the = printed page,
over and above the regular run of document body -- we = have the page
header and footer mechanisms that the output routine = already calls.  i
don't see what a `printing' bop-hook is going to do = that these
mechanisms don't already enable.  hell, the = header/footer mechanisms
already _are_ hooks.

what we don't have is the means to execute bits of = code that directly
affect the way the output routine operates.  if = you want to affect the
way footnotes are generated, you have to patch the = output routine.
there's no existing hook that helps you -- you have = to get in there
and patch.

now, i've no clear model of how we might write an = output routine that
would facilitate this sort of thing, but it sure as = hell isn't by
adding bits of code at the start of a page.

robin

speaking for myself.  i don't know what frank's = up to either.

------_=_NextPart_001_01BF87BD.4FF9C180--