X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1339" "Sun" "6" "December" "1998" "10:42:17" "-0500" "Y&Y, Inc." "support@YANDY.COM" nil "25" "Re: What is \"base\" LaTeX" "^Date:" nil nil "12" nil "What is \"base\" 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 QAA29815; Sun, 6 Dec 1998 16:43:02 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <6.F377D5FD@listserv.gmd.de>; Sun, 6 Dec 1998 16:43:01 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 411369 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 6 Dec 1998 16:42:57 +0100 Received: from mail-out-0.tiac.net (mail-out-0.tiac.net [199.0.65.247]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id QAA03348 for ; Sun, 6 Dec 1998 16:42:54 +0100 (MET) Received: from mail-out-3.tiac.net (mail-out-3.tiac.net [199.0.65.15]) by mail-out-0.tiac.net (8.8.8/8.8.8) with ESMTP id KAA20651 for ; Sun, 6 Dec 1998 10:42:40 -0500 (EST) (envelope-from support@YandY.com) Received: from DENALI (p58.tc2.metro.MA.tiac.com [209.61.75.187]) by mail-out-3.tiac.net (8.8.7/8.8.7) with SMTP id KAA17074 for ; Sun, 6 Dec 1998 10:42:38 -0500 (EST) (envelope-from support@YandY.com) X-Sender: yandy@pop.tiac.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <4.1.19981206103413.01e099b0@pop.tiac.net> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <19981206151331.A12791@maths.tcd.ie> Date: Sun, 6 Dec 1998 10:42:17 -0500 From: "Y&Y, Inc." Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: What is "base" LaTeX Status: R X-Status: X-Keywords: X-UID: 3047 At 10:13 AM 98/12/06 , you wrote: >Ps If xdvi worked as advertised it would itself be a TeX browser. Maybe this is something that merits more discussion. DVIWindo can be launched when a browser hits a DVI file. It also supports hyper-text linkage, including the ability to launch applications to deal with included file references to say PDF, HTML, TIFF files etc. (although it can also display TIFF directly). And since DVI files are compact it is very fast. But there are obstacles to making this sort of thing a reasonable alternative. One is that the DVI files are compact in part because they do not include fonts, so this works only if everyone has the fonts that are used. That probably means using CM fonts for everything. Included figures are an obstacle since these are not included in the DVI file, so would have to be fetched in a separate interaction. And different DVI previewer support very different collections of graphics (TIFF, BMP, GIF, JPEG, PICT, WMF, EPS, EPSI, TPIC, EEPIC, etc. etc.). And unless several `DVI browsers' support the some basic set of features (which may have big differences in implementation costs on different platforms), there won't be much of an incentive for people to use this as a medium for document distribution. Y&Y, Inc. http://www.YandY.com/news.htm mailto:support@YandY.com