Return-Path: owner-linux-activists@Niksula.hut.fi
Return-Path: <owner-linux-activists@Niksula.hut.fi>
Received: from joker.cs.hut.fi by hydra.Helsinki.FI (4.1/SMI-4.1/36)
	id AA29606; Fri, 5 Mar 93 09:01:17 +0200
Received: from joker.cs.hut.fi by niksula.hut.fi id <62472-4>; Fri, 5 Mar 1993 09:00:26 +0200
From: "Linux Activists" <linux-activists@Niksula.hut.fi>
To: "Linux-Activists" <linux-activists@Niksula.hut.fi>
Reply-To: "Linux-Activists" <linux-activists@Niksula.hut.fi>
X-Note1: Remember to put 'X-Mn-Key: DOC' to your mail body or header
Subject: Linux-Activists - DOC Channel digest. 93-2-5-2:49
X-Mn-Key: DOC
Sender: owner-linux-activists@Niksula.hut.fi
Message-Id: <93Mar5.090026eet.62472-4@niksula.hut.fi>
Date: Fri, 5 Mar 1993 09:00:22 +0200
Status: RO
X-Status: 


Topics:
	 Re: Man Project


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

From: eds2@cornell.edu (Eric Scharff)
Subject: Re: Man Project
Date: Fri, 5 Mar 1993 04:19:53 +0200



>From: michael@gandalf.moria (Michael Haardt)
>Subject: Re: Re: Man Project
>Date: Tue, 2 Mar 1993 17:23:55 +0200
>
>For now groff will be used, of course.  Further, a roff -> texinfo
>filter is needed to convert current linux and other manual pages.  For
>now means, I have no idea yet when the big change (tm) will happen.
>However it means, that cryptic roff code and non-standard macros should
>be avoided.  That filter will not disappear after, it will stay useful
>for years and years I think.  Btw: most manual pages *are* clean, so I
>don't expect too much problems in this area.
[...]
>Agreed.  Personally, I still like roff very much and I would hate to see
>it disappear, but then again ... I am not going to document the C
>library, so obviously I can't say much.

        Yes, we should continue to use groff for our man work for now.  In
fact, the decision of the GNU team to document their section 3 in texinfo
format does not change our plans.  Groff and texinfo man pages need not be
mutually exclusive.  Before the FSF completes its work, we should have a
man (and xman) that can handle *roff and texinfo pages.  Included with this
would be a info reader that does not need emacs underneath it.
        For now, I think we should remain writing groff pages.  We can
always change that in the future.

-Eric Scharff
 eds2@cornell.edu




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

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