Xref: utzoo comp.text:8051 alt.hypertext:751 Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewse!danj1 From: Dan_Jacobson@ATT.COM Newsgroups: comp.text,alt.hypertext Subject: Re: Hypertext and CASE for on-line docs (long) Message-ID: Date: 22 Feb 91 17:49:46 GMT References: <1991Feb22.154333.10409@cbnewsl.att.com> Sender: danj1@cbnewse.att.com (Dan Jacobson) Reply-To: Dan_Jacobson@ATT.COM Organization: AT&T-BL, Naperville IL, USA Lines: 20 In-Reply-To: saal@floyd.ATT.COM's message of Fri, 22 Feb 91 15:43:33 GMT >>>>> On Fri, 22 Feb 91 15:43:33 GMT, saal@floyd.ATT.COM (Sam Saal,1A-110,6956,Cap Gemini) said: Sam> Followups-To: comp.text Isn't that supposed to be in the header? :-) Sam> My project is considering implementing a Hypertext interface to our Sam> documentation. Perhaps consider GNU Emacs' TeXinfo, a marriage between two great quazi public domain tools: GNU Emacs and TeX. Hundreds of pages of tree/menuized manuals are as close as $ emacs -f info to many users as we speak. [Admittedly I don't read alt.hypertext and lack other hypertext knowledge.] There even is a LaTeXinfo, and standalone info browsers using this format. Tune in to the gnu.* and comp.text.tex groups for more info. -- Dan_Jacobson@ATT.COM Naperville IL USA +1 708-979-6364 Brought to you by Super Global Mega Corp .com