Re: hyper-TeX and standards for client-side extensions

• Mail folder: WWW Talk Jan 94-present
• Next message: Tony Sanders: "Re: Inlined image format "
• Previous message: ellson@hotsand.att.com: "Re: Inlined image format"
• In-reply-to: burchard@geom.umn.edu: "hyper-TeX and standards for client-side extensions"
• References: burchard@geom.umn.edu: "hyper-TeX and standards for client-side extensions"
• Reply: Henning G. Schulzrinne: "Re: hyper-TeX and standards for client-side extensions"
• Reply: burchard@geom.umn.edu: "Re: hyper-TeX and standards for client-side extensions"

Message-id: <IhFP0hoB0KGWMYkwcj@holmes.parc.xerox.com>
Date: 	Tue, 25 Jan 1994 15:50:05 PST
Sender: Bill Janssen <janssen@parc.xerox.com>
From: Bill Janssen <janssen@parc.xerox.com>
To: www-talk@www0.cern.ch, burchard@geom.umn.edu
Subject: Re: hyper-TeX and standards for client-side extensions
In-reply-to: <9401252250.AA19881@mobius.geom.umn.edu>
References: <9401252250.AA19881@mobius.geom.umn.edu>
Content-Length: 472

I think a more realistic and useful thing would be to add a Hypertext
Extension to Postscript (which, of course, TeX document can convert
into).  Then you could handle all kinds of different document formats,
including PC word processor formats, and you could also handle color,
embedded bitmaps, and other things outside of TeX's scope.  The code to
do the client-side rendering is already available
(ghostscript/ghostview), and I've seen it embedded in X widgets.

Bill