Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Thu, 28 Sep 2000 21:54:24 +0200 (MEST) 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 VAA13423 for ; Thu, 28 Sep 2000 21:54:24 +0200 (MEST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C02985.E6721800" Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id e8SJsNG26633 for ; Thu, 28 Sep 2000 21:54:24 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <5.203653F2@mail.listserv.gmd.de>; Thu, 28 Sep 2000 21:54:23 +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 471956 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 28 Sep 2000 21:54:19 +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 VAA01239 for ; Thu, 28 Sep 2000 21:54:18 +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 VAA30910 for ; Thu, 28 Sep 2000 21:54:19 +0200 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 VAA27354 for ; Thu, 28 Sep 2000 21:54:18 +0200 (MET DST) Received: from pallas.cl.cam.ac.uk ([128.232.8.88] helo=cl.cam.ac.uk ident=rf) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 13ejl4-0003aW-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Thu, 28 Sep 2000 20:54:18 +0100 In-Reply-To: Your message of "Thu, 28 Sep 2000 21:32:06 +0200." Return-Path: Content-class: urn:content-classes:message Subject: Re: hyperref Date: Thu, 28 Sep 2000 20:54:18 +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: 3620 This is a multi-part message in MIME format. ------_=_NextPart_001_01C02985.E6721800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hans aberg writes: > It appears to me that the "hyperref" package ought to appear in the > "required" part of the LaTeX distribution: we actually discussed this (and one or two other packages) early last year; we generally felt it was a good idea ... but that at the time such a change would be difficult. now that heiko oberdiek is fully in charge (sebastian rahtz was nominally still the maintainer back then), it may be worth discussing it further, if heiko is interested. > The development moves towards more and more wholly electronic = documents, > and hyperlinks aid a great deal in reading such documents, especially = when > douments are large, or technical in nature. (For example, the LaTeX > distribution documents would benefit a great deal by this. :-) ) your reasoning is entirely valid, but you should understand that pragmatic considerations also contrive to bite into what might be optimal. we couldn't simply, as a project, take over maintenance of a package of such a magnitude as hyperref; so we need to find a maintainer before bringing it into the ambit the project. heiko is an active and industrious maintainer, but i haven't asked him whether he would welcome joining a formal structure such as that of latex maintenance. Robin Fairbairns, Cambridge ------_=_NextPart_001_01C02985.E6721800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: hyperref

hans aberg writes:

> It appears to me that the "hyperref" = package ought to appear in the
> "required" part of the LaTeX = distribution:

we actually discussed this (and one or two other = packages) early last
year; we generally felt it was a good idea ... but = that at the time
such a change would be difficult.  now that = heiko oberdiek is fully in
charge (sebastian rahtz was nominally still the = maintainer back then),
it may be worth discussing it further, if heiko is = interested.

> The development moves towards more and more = wholly electronic documents,
> and hyperlinks aid a great deal in reading such = documents, especially when
> douments are large, or technical in nature. (For = example, the LaTeX
> distribution documents would benefit a great = deal by this. :-) )

your reasoning is entirely valid, but you should = understand that
pragmatic considerations also contrive to bite into = what might be
optimal.  we couldn't simply, as a project, take = over maintenance of a
package of such a magnitude as hyperref; so we need = to find a
maintainer before bringing it into the ambit the = project.  heiko is an
active and industrious maintainer, but i haven't = asked him whether he
would welcome joining a formal structure such as that = of latex
maintenance.

Robin Fairbairns, Cambridge

------_=_NextPart_001_01C02985.E6721800--