I won't give up on groff.texinfo. This consequently means that we
need a groff2texinfo converter (or groff2info to get the more
important info files) in case the source files are in groff
format. Personally, I *really* like the indexing features of
`info' which are quite powerful. I'm not aware of a different
indexing system which is freely available (but I must admit that I
haven't done an extensive search).
I agree. However, as a GNU program, GNU users are going to
automatically look at info, not man, (plus, that's the developer
standard). As much of an irony that it may seem, the manual for
groff would be in groff for the sake of portability to other UNIX
platforms. I think the manual should be maintained seperately and
simply as a basic reference, refering to the info file for more
complicated or detailed information.
groff.texinfo contains quite dry material. It will never become
a first-read document. Wouldn't it be more useful to create
an introductory document from scratch, probably taking the
introductory stuff from groff.texinfo (which would be consequently
removed)?
I think that we should build on the work already done, not start
over. However, I think that revision is needed for the
sake of simplicity and comfort. The first thing to do would be
to setup an organized structure of what we want in the groff info
manual, then rearrange what we have to fit in that structure,
then add content to complete the structure.
_______________________________________________
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
