X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1841" "Mon" "14" "December" "1998" "19:05:31" "+0000" "Timothy Murphy" "tim@MATHS.TCD.IE" nil "45" "Re: portable LaTeX" "^Date:" nil nil "12" nil "portable LaTeX" 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 UAA30852; Mon, 14 Dec 1998 20:05:40 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <8.95A13196@listserv.gmd.de>; Mon, 14 Dec 1998 20:05:39 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 413556 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 14 Dec 1998 20:05:35 +0100 Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with SMTP id UAA06216 for ; Mon, 14 Dec 1998 20:05:31 +0100 (MET) Received: from boole.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Dec 98 19:05:32 +0000 (GMT) References: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Message-ID: <19981214190530.B8449@maths.tcd.ie> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: ; from Hans Aberg on Mon, Dec 14, 1998 at 07:19:17PM +0100 Date: Mon, 14 Dec 1998 19:05:31 +0000 From: Timothy Murphy 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: 3116 On Mon, Dec 14, 1998 at 07:19:17PM +0100, Hans Aberg wrote: > >It's madness, in my view, to modify the TeX engine > >in order to allow inclusion of particular graphic formats. > > What modifications do they do in pdfTeX? I don't understand the question. Since TeX does not understand graphics in any format while pdfTeX does, there is obviously a modification, as indeed is clear from pdftex.ch @# {data structure of images; for |pdf_image_node| and |pdf_ref_form_node| the identifier of XObject will be store in |obj_info| of coresponding object in |obj_tab|} @d pdf_image_node_size == 5 {size of whatsit node for image} @d pdf_image_info(#) == mem[# + 4].int {pointer to hold data structures in external \.{libpng} library} @d obj_image_ptr == obj_aux {pointer to image structure} However, my main point was that since pdftex is a single monolithic program, every additional graphics format -- PDF, PS, TIFF, etc -- must involve further modification to pdfTeX itself. > >While Thanh's pdfTeX is a marvellous piece of work, > >which satisfied an urgent need, > >in my view it is fundamentally misconceived, > >and will in time be replaced by a version based on possibly extended DVI. > > But will an extended DVI suffice as a new byte-code for WWW publishing? I take more or less the opposite view to that generally expressed here. In my view, it is up to browsers to accept generally accepted formats like PDF or DVI -- it's not up to the outside world to try to convert information into the format expected by the browser. I would expect browsers to define something like a Java interface, with the understanding that they will display anything which implements this interface. -- Timothy Murphy e-mail: tim@maths.tcd.ie tel: +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland