Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Fri, 29 Sep 2000 13:30:52 +0200 (MEST) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id NAA16875 for ; Fri, 29 Sep 2000 13:30:52 +0200 (MEST) MIME-Version: 1.0 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id e8TBUpd22344 for ; Fri, 29 Sep 2000 13:30:51 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C02A08.B91A7E00" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <10.F2D62960@mail.listserv.gmd.de>; Fri, 29 Sep 2000 13:30:51 +0200 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 471578 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 29 Sep 2000 13:30:48 +0200 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 NAA09438 for ; Fri, 29 Sep 2000 13:30:47 +0200 (MET DST) 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 NAA35126 for ; Fri, 29 Sep 2000 13:30:47 +0200 Received: from venus.open.ac.uk (venus.open.ac.uk [137.108.143.2]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id NAA06398 for ; Fri, 29 Sep 2000 13:30:47 +0200 (MET DST) Received: from fell.open.ac.uk by venus with SMTP Local (Mailer 3.1) with ESMTP; Fri, 29 Sep 2000 12:29:05 +0100 Received: (from car2@localhost) by fell.open.ac.uk (8.9.3+Sun/8.9.1) id MAA15899; Fri, 29 Sep 2000 12:29:05 +0100 (BST) In-Reply-To: <14803.54227.259547.782919@spqr2.oucs.ox.ac.uk> References: <14803.54227.259547.782919@spqr2.oucs.ox.ac.uk> Return-Path: X-Mailer: VM 6.76 under Emacs 20.7.1 X-Authentication-Warning: fell.open.ac.uk: car2 set sender to car2@fell.open.ac.uk using -f Content-class: urn:content-classes:message Subject: Re: hyperref Date: Fri, 29 Sep 2000 12:29:05 +0100 Message-ID: <14804.32001.222549.964951@fell.open.ac.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Chris Rowley" 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: 3626 This is a multi-part message in MIME format. ------_=_NextPart_001_01C02A08.B91A7E00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sebastian is essentialy correct in his analysis of the history and current status wrt the LaTeX kernel and required: > I think its more fundamental than that, as discussed as far back as > 1993 - hyperref does not fit into the model of LaTeX properly, and > rides roigh-shod over LaTeX innards when it feels like it. To add it > to "required" would imply that the kernel team felt that it reliably > collaborated with kernel packages, which would simply be untrue. > > To do it right, bits of LaTeX need a rewrite, taking into account the > needs of hyperref. This is what Context has done, of course, > integrating the stuff into the kernel. > What we have not done yet, due to `stafff shortages', is any detailed work on building the requirements of multi-use documents (via hyperef or any other pakage) into the new experimental work that I am sure you are all right now busily testing. chris ------_=_NextPart_001_01C02A08.B91A7E00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: hyperref

Sebastian is essentialy correct in his analysis of the = history and
current status wrt the LaTeX kernel and = required:

> I think its more fundamental than that, as = discussed as far back as
> 1993 - hyperref does not fit into the model of = LaTeX properly, and
> rides roigh-shod over LaTeX innards when it = feels like it. To add it
> to "required" would imply that the = kernel team felt that it reliably
> collaborated with kernel packages, which would = simply be untrue.
>
> To do it right, bits of LaTeX need a rewrite, = taking into account the
> needs of hyperref. This is what Context has = done, of course,
> integrating the stuff into the kernel.
>

What we have not done yet, due to `stafff shortages', = is any detailed
work on building the requirements of multi-use = documents (via hyperef
or any other pakage) into the new experimental work = that I am sure you
are all right now busily testing.


chris

------_=_NextPart_001_01C02A08.B91A7E00--