From xemacs-m  Tue Jan 21 13:40:19 1997
Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5])
          by xemacs.org (8.8.4/8.8.4) with SMTP
	  id NAA00222 for <xemacs-beta@xemacs.org>; Tue, 21 Jan 1997 13:40:19 -0600 (CST)
Received: from infodock.com (wave.infodock.com [206.13.40.192]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with ESMTP id LAA07669 for <xemacs-beta@xemacs.org>; Tue, 21 Jan 1997 11:39:47 -0800
Received: (from weiner@localhost) by infodock.com (8.7.4/8.7.3) id LAA14266; Tue, 21 Jan 1997 11:35:29 -0800
Date: Tue, 21 Jan 1997 11:35:29 -0800
From: Bob Weiner <weiner@infodock.com>
Message-Id: <199701211935.LAA14266@infodock.com>
To: xemacs-beta@xemacs.org
In-reply-to: <199701211743.KAA00560@branagh.lanl.gov> (message from John Turner on Tue, 21 Jan 1997 10:43:40 -0700)
Subject: Re: Should we convert XEmacs Texinfo documents to HTML?


>>>>> "JT" == John Turner <turner@xdiv.lanl.gov> writes:

   JT> I, too, like very much the ability to view documentation in [X]Emacs.
   JT> However, the limitations of Texinfo, specifically

   JT> o the inability to do math, and
   JT> o the inability to include graphics

Both of these are of course possible in the printed form of manuals by
dropping into TeX using @iftex markup.  In fact, the InfoDock manual, written
in Texinfo, has nicely embedded screen shots in the printed form and
hyperlinks in the Info form that when clicked display the screen shots
using a graphics viewer such as xv.  A future release of the XEmacs manual
will likely have screen shots as well.  We could probably inline the graphics
in the XEmacs Info viewer as well with a bit of work.

When HTML can produce the kinds of documents that Scribe could in the early
1980s, someone should wake us up and then have look at using it as a book
production markup language.

Cheers,

Bob



