Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Mon, 2 Oct 2000 00:06:00 +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 AAA26912 for ; Mon, 2 Oct 2000 00:05:59 +0200 (MEST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C02BF3.C8115400" 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 e91M5wd22818 for ; Mon, 2 Oct 2000 00:05:59 +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 <0.0131E103@mail.listserv.gmd.de>; Mon, 2 Oct 2000 0:05:58 +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 471128 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 2 Oct 2000 00:00:16 +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 XAA12032 for ; Sun, 1 Oct 2000 23:57:41 +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 XAA27502 for ; Sun, 1 Oct 2000 23:57:42 +0200 Received: from csc.albany.edu (sarah.albany.edu [169.226.1.103]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id XAA09793 for ; Sun, 1 Oct 2000 23:57:41 +0200 (MET DST) Received: from hilbert.math.albany.edu (hilbert.math.albany.edu [169.226.23.52]) by csc.albany.edu (8.9.3/8.9.3) with ESMTP id RAA02847; Sun, 1 Oct 2000 17:55:36 -0400 (EDT) Received: (from hammond@localhost) by hilbert.math.albany.edu (8.9.3/8.9.3) id RAA13711; Sun, 1 Oct 2000 17:55:34 -0400 (EDT) Return-Path: Content-class: urn:content-classes:message Subject: Re: hyperref Date: Sun, 1 Oct 2000 22:55:34 +0100 Message-ID: <200010012155.RAA13711@hilbert.math.albany.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "William F. Hammond" 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: 3629 This is a multi-part message in MIME format. ------_=_NextPart_001_01C02BF3.C8115400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Chris Rowley writes: > 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. Is it correct to assume that "multi-use" in the context of LaTeX 3 documents refers only to (1) regular latex and (2) pdflatex? If so, is it agreed that broader senses of "multi-use" would stretch LaTeX, the language (as it will be in LaTeX 3), too far? Thanks. -- Bill ------_=_NextPart_001_01C02BF3.C8115400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: hyperref

Chris Rowley writes:

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

Is it correct to assume that "multi-use" in = the context of LaTeX 3
documents refers only to (1) regular latex and (2) = pdflatex?

If so, is it agreed that broader senses of = "multi-use" would stretch
LaTeX, the language (as it will be in LaTeX 3), too = far?

Thanks.

          &nbs= p;            = ;            = -- Bill

------_=_NextPart_001_01C02BF3.C8115400--