X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1601" "Wed" "10" "September" "1997" "09:29:16" "+0100" "Sebastian Rahtz" "s.rahtz@ELSEVIER.CO.UK" nil "30" "Re: HyperLaTeX" "^Date:" nil nil "9" nil "HyperLaTeX" nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.5/8.8.5) with ESMTP id KAA28966; Wed, 10 Sep 1997 10:40:47 +0200 (MET DST) Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <1.3EEA8FE0@listserv.gmd.de>; Wed, 10 Sep 1997 10:39:14 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 196536 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 10 Sep 1997 10:39:56 +0200 Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by relay.urz.uni-heidelberg.de (8.7.6/8.7.4) with ESMTP id KAA25602 for ; Wed, 10 Sep 1997 10:39:54 +0200 (MET DST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by pillar.elsevier.co.uk (8.8.5/8.8.5) with ESMTP id JAA27060 for ; Wed, 10 Sep 1997 09:39:52 +0100 (BST) Received: from SRAHTZ (actually host srahtz.elsevier.co.uk) by snowdon.elsevier.co.uk with SMTP (PP); Wed, 10 Sep 1997 09:39:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: X-Mailer: VM 6.33 under Emacs 19.34.4 Message-ID: <1270-Wed10Sep1997092916+0100-s.rahtz@elsevier.co.uk> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Date: Wed, 10 Sep 1997 09:29:16 +0100 From: Sebastian Rahtz Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: HyperLaTeX Status: R X-Status: X-Keywords: X-UID: 2299 > I understand that the \special{foo} command just puts the text "foo" into > the output. Perhaps the LaTeX project should define (if not already done) a > standard to identify which protocol the text belongs to, but no more. For > example \special{html:foo} would identify "foo" as being html, whereas > \special{url:foo} would identify "foo" as a URL. the hypertex project already does some of this standardization, if you want to follow it. not sure what else is needed. > I think HyperTeX defines hyperlinks in terms of HTML, as > \special{html:foo}. My hunch is that this is a bad idea, as HTML is in > itself a markup language (how to combine the different graphical outputs?). > The problem is that HTML consists of two parts, the hyperlink stuff and the > graphical markup stuff, and it is not possible to get only the hyperlink i dont see what you are getting at. the hypertex specials define a set of \special conventions which look like the HTML equivalents, thats all > It seems me that \label and \bibitem could be used to generate URL names > (locations within a file), and \ref, \eqref, and \cite could be used to > generate hyperlinks within a file. For external ref's (to other doc's), one quite. thats what hyperref does > In addition, one could add a few commands, such as indicating a base URL if thats in HyperTeX > The idea is that a lot of people already writes manuscripts using \label, > etc, and one should be able use that contextual information to > automatically generate helpful hyperlinks. try using hyperref. it all just happens Sebastian