> Writing all of that in groff would be a pain. More of my time would be spent > understanding the syntax than it would be focusing on the content. Texinfo's > syntax is much more readable and easy to remember. And the HTML and PDF > output look nice to read.
* I have patches from 2001 to texi2roff that add codes to the "me" table so "texi2roff -me $texiname | groff -me" could process most of the gnu texi files at that time. http://williambader.com/pat/texi2roff.pat.bz2 > I guess Markdown or reStructuredText would be more friendly to new > contributors since many do not know Texinfo. Pandoc https://pandoc.org/ can convert between a number of formats. In theory, it can convert markdown and rst to texinfo. Maybe with care it would be possible to come up with a set of conventions for markdown, maybe with a preprocessing pass, to have pandoc produce texinfo that can print well. William ________________________________ From: [email protected] <[email protected]> on behalf of Collin Funk <[email protected]> Sent: Saturday, September 20, 2025 4:05 PM To: Alejandro Colomar <[email protected]> Cc: Pádraig Brady <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Re: Move GNU manual pages to the Linux man-pages project Alejandro Colomar <[email protected]> writes: > Hi Pádraig, > > On Sat, Sep 20, 2025 at 06:01:21PM +0100, Pádraig Brady wrote: >> > > All of the man pages have links to the info docs for full documentation. >> > >> > I know. However, many users don't enjoy the info docs. >> >> I my experience user don't enjoy the info _reader_, while the docs are fine. >> The full docs are on the web though and also linked from each man page. > > Yeah, the info online docs are much nicer. However, I (and others) > don't enjoy going online for documentation, when offline documentation > is available. I wish distributions installed the HTML docs to /usr/share/doc/coreutils, or somewhere similar (and substitute package name for other packages). The gnu.org site is down or takes ages to load frequently nowadays. That said, I have seen complaints about the Coreutils man pages being "incomplete". However, it is grown on me personally. I use the man pages as a quick reference when I want to find an option or understand what it does. And the info page for examples and/or commentary that is too long to reasonably fit in --help. Writing all of that in groff would be a pain. More of my time would be spent understanding the syntax than it would be focusing on the content. Texinfo's syntax is much more readable and easy to remember. And the HTML and PDF output look nice to read. I guess Markdown or reStructuredText would be more friendly to new contributors since many do not know Texinfo. However, I haven't seen good PDFs generated by them (though I concede that I very well could be unaware of examples). Collin
