-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
--- Andreas L. Delmelle [EMAIL PROTECTED]
I'm not too fond of this type of arguments:
everybody/nobody else is doing it, so why
shouldn't/should we...
Hey, I like that argument! For example, no other
Apache project
-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Manpages are usually for C-language
Correct so far.
Unix-specific applications, no?
Hmm... The manpages themselves obviously are Unix-specific, but I'm not so
sure whether the applications always are or necessarily have
--- Andreas L. Delmelle [EMAIL PROTECTED]
wrote:
My thinking is that since Xalan, Xerces, Cocoon,
Batik, etc., don't offer them, then we shouldn't
either.
Yuck! I'm not too fond of this type of arguments:
everybody/nobody else is
doing it, so why shouldn't/should we... This is no
Unless Docbook can generate manpages, we would also
have the problem of needing to maintain two sets of
documentation (online and manpage) to say the same
thing.
Though never generated a man page on my own, DocBook seems to do it.
Have a look at:
Great! Thanks for the info.
Glen
--- Christian Z. [EMAIL PROTECTED] wrote:
Unless Docbook can generate manpages, we would
also
have the problem of needing to maintain two sets
of
documentation (online and manpage) to say the
same
thing.
Though never generated a man page on
Team,
What do others think of this question?
If all our *nix users would benefit from it, I'm all for (--but I'm not all
too familiar with the syntax of manpages... yet ;-) Is the format generic
enough to be supported by all *nix platforms, or would we have to write
separate ones for Debian /
Manpages are usually for C-language Unix-specific
applications, no? I'm not sure of the future they
have compared to website documentation, Docbook, etc.
Unless Docbook can generate manpages, we would also
have the problem of needing to maintain two sets of
documentation (online and manpage) to
