Return-Path: owner-linux-activists@joker.cs.hut.fi
Received: from joker.cs.hut.fi (root@joker.cs.hut.fi [130.233.40.32]) by keos.Helsinki.FI (8.6.4/H45) with SMTP id MAA10735 for <wirzeniu@cs.Helsinki.FI>; Sat, 11 Dec 1993 12:44:21 +0200
Received: from joker.cs.hut.fi by niksula.hut.fi id <64105-1>; Sat, 11 Dec 1993 12:43:25 +0200
From: "Linux Activists" <linux-activists@joker.cs.hut.fi>
To: "Linux-Activists" <linux-activists@joker.cs.hut.fi>
Reply-To: "Linux-Activists" <linux-activists@joker.cs.hut.fi>
X-Note1: Remember to put 'X-Mn-Key: DOC' to your mail body or header
Subject: Linux-Activists - DOC Channel digest. 93-11-11-6:31
X-Mn-Key: DOC
Sender: owner-linux-activists@joker.cs.hut.fi
Message-Id: <93Dec11.124325eet.64105-1@niksula.hut.fi>
Date: Sat, 11 Dec 1993 12:43:19 +0200
Status: RO
X-Status: 


Topics:
	 Re: Linux-Activists - DOC Channel digest. 93-11-10-2:26


----------------------------------------------------------------------

From: mdw@SunSite.unc.edu (Matt Welsh)
Subject: Re: Linux-Activists - DOC Channel digest. 93-11-10-2:26
Date: Sat, 11 Dec 1993 07:06:44 +0200


Thanks to everyone for comments on OTF. I'm currently looking at using
SGML with an "OTF DTD" for implementing this. Someone pointed out a nice
tool, QWERTZ, which can convert SGML to TeX and nroff. It seems that
info would not be hard to produce.

> From: okir@monad.swb.de (Olaf Kirch)
>
> Stressing the word *could*. Given that TeXinfo has these features, too,
> this leaves me wondering why documentation doesn't get written (and,
> even less, read) ;)

My main problem with TeXinfo is that it doesn't automatically generate
@node entries for you. (Maybe LaTeXinfo does.) Also, ASCII produced by
texi2roff is not very good quality. :(

All comments have been helpful. I'm going to take another look at SGML
tools and see what I can find. 




------------------------------

End of DOC Digest
*****************
-------
