X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["977" "Wed" "10" "September" "1997" "12:53:42" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "20" "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 MAA09237; Wed, 10 Sep 1997 12:53:29 +0200 (MET DST) Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <6.C5066716@listserv.gmd.de>; Wed, 10 Sep 1997 12:51:50 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 196581 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 10 Sep 1997 12:52:30 +0200 Received: from mail.nada.kth.se (root@mail.nada.kth.se [130.237.222.92]) by relay.urz.uni-heidelberg.de (8.7.6/8.7.4) with ESMTP id MAA00457 for ; Wed, 10 Sep 1997 12:52:25 +0200 (MET DST) Received: from [130.237.37.138] (sl123.modempool.kth.se [130.237.37.149]) by mail.nada.kth.se (8.8.4/8.8.4) with SMTP id MAA16112 for ; Wed, 10 Sep 1997 12:52:57 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project Date: Wed, 10 Sep 1997 12:53:42 +0200 From: Hans Aberg 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: 2300 Sebastian Rahtz writes: >the hypertex project already does some of this standardization, if you want to >follow it. not sure what else is needed. So how does the hypertex protocol work together with other protocols, like embedded PS or non-GIF pictures? Does every protocol invent its own syntax to identify itself? > > 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 Well, the HTML standard is evolving, and one would then want to have access to the new hyperlink features, but not the markup features. So one would really want to work with a hyperlink protocol, and not HTML. Hans Aberg * AMS member: Listing * Email: Hans Aberg