X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1569" "Tue" "15" "December" "1998" "12:07:55" "+0100" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "31" "Re: portable LaTeX" "^Date:" nil nil "12" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id MAA27853; Tue, 15 Dec 1998 12:39:39 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <14.92CA50C9@listserv.gmd.de>; Tue, 15 Dec 1998 12:26:15 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 413332 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 15 Dec 1998 12:26:11 +0100 Received: from mail0.nada.kth.se (mail0.nada.kth.se [130.237.222.70]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id MAA24555 for ; Tue, 15 Dec 1998 12:25:55 +0100 (MET) Received: from [130.237.37.21] (sl01.modempool.kth.se [130.237.37.21]) by mail0.nada.kth.se (8.8.7/8.8.7) with ESMTP id MAA16459 for ; Tue, 15 Dec 1998 12:25:50 +0100 (MET) X-Sender: su95-hab@mail.nada.kth.se References: ; from Hans Aberg on Mon, Dec 14, 1998 at 10:18:24PM +0100 <13941.11832.164081.296097@srahtz>; <13938.39518.68424.927988@fell.open.ac.uk> <199812092035.VAA16014@na6.mathematik.uni-tuebingen.de> <199812141457.IAA15514@dcdrjh.fnal.gov> <13941.11832.164081.296097@srahtz> <19981214170857.D29182@maths.tcd.ie> <19981214190530.B8449@maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <19981215032328.B3729@maths.tcd.ie> Date: Tue, 15 Dec 1998 12:07:55 +0100 From: Hans Aberg Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: portable LaTeX Status: R X-Status: X-Keywords: X-UID: 3130 At 03:23 +0000 1998/12/15, Timothy Murphy wrote: >> >> But will an extended DVI suffice as a new byte-code for WWW publishing? > >I don't know what that means; >I take it that any format in the world can be sent over the "Web". >Whether a particular program (browser) can display it >is simply up to the program. >There is nothing special about browsers, as far as I can see. >xdvi is a program that can display remote DVIs; >if enough people used it like this it would be called a browser. The display of the WWW browser itself must use a language of some kind to display its graphicla information, links and such (telling where each spot is supposed to be), not to be confused with the language originating the display information. Turn that more basic language into a byte code; then any other language (DVI, PS, PDF, ...) can display by first converting to that language: For every new such language, you then need a plugin that can do the translation, but that is all. >I don't know what a "WWW byte-code" is, >and so I don't understand the rest of your posting. So this would be like the JVM byte-code: Once you have the byte-code standard and the JVM, if the byte-code language is sufficiently general, one can use several different computer languages to translate onto that byte-code language. The point is that it is platform independent. Hans Aberg * Email: Hans Aberg * Home Page: * AMS member listing: