From: Michael Greenberg <michael@greenberg.science>
To: William Bader <williambader@hotmail.com>,
Collin Funk <collin.funk1@gmail.com>,
Alejandro Colomar <alx@kernel.org>
Cc: "Pádraig Brady" <P@draigbrady.com>,
"coreutils@gnu.org" <coreutils@gnu.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: Move GNU manual pages to the Linux man-pages project
Date: Mon, 22 Sep 2025 11:06:18 -0400 [thread overview]
Message-ID: <87sege1q8l.fsf@hippogriff> (raw)
In-Reply-To: <PA3P190MB24382227EA61EC2758D5AA11C410A@PA3P190MB2438.EURP190.PROD.OUTLOOK.COM>
On 2025-09-20 at 10:31:31 PM, William Bader wrote:
[snip]
>> 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.
I've been very happy using pandoc to generate manpages from Markdown for
ffs:
- Markdown: <https://github.com/mgree/ffs/blob/main/docs/ffs.1.md>
- Makefile to generate manpage: <https://github.com/mgree/ffs/blob/main/man/Makefile>
- Output: <https://github.com/mgree/ffs/blob/main/man/ffs.1>
I haven't tried generating texinfo (I quite dislike the info reader and
avoid using it), but I suspect the output would be satisfactory. While I
understand the GNU bias in favor of info, I would support any efforts to
improve the manpages (which are, imo, more accessible).
Cheers,
Michael
next prev parent reply other threads:[~2025-09-22 15:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 16:08 Move GNU manual pages to the Linux man-pages project Alejandro Colomar
2025-09-20 16:27 ` Sam James
2025-09-20 16:50 ` Alejandro Colomar
2025-09-20 17:00 ` Alejandro Colomar
2025-09-20 16:34 ` Pádraig Brady
2025-09-20 16:55 ` Alejandro Colomar
2025-09-20 17:01 ` Pádraig Brady
2025-09-20 17:04 ` Alejandro Colomar
2025-09-20 20:05 ` Collin Funk
2025-09-20 21:05 ` Alejandro Colomar
2025-09-20 23:02 ` Collin Funk
2025-09-21 8:36 ` Alejandro Colomar
[not found] ` <PA3P190MB24382227EA61EC2758D5AA11C410A@PA3P190MB2438.EURP190.PROD.OUTLOOK.COM>
2025-09-20 23:18 ` Collin Funk
2025-09-22 15:06 ` Michael Greenberg [this message]
2025-09-20 17:42 ` Jakub Wilk
2025-09-20 21:10 ` Alejandro Colomar
2025-09-20 21:22 ` Collin Funk
2025-09-21 8:28 ` Bernhard Voelker
2025-09-21 20:00 ` Chuck Wolber
2025-09-21 12:02 ` Arsen Arsenović
2025-09-21 12:53 ` Alejandro Colomar
2025-09-25 14:04 ` Arsen Arsenović
2025-09-25 14:31 ` Alejandro Colomar
2025-09-29 9:46 ` Arsen Arsenović
2025-09-29 10:33 ` Alejandro Colomar
2025-09-29 21:26 ` Arsen Arsenović
2025-09-29 21:38 ` Alejandro Colomar
2025-09-29 21:41 ` Pádraig Brady
2025-09-29 23:27 ` Alejandro Colomar
2025-09-30 10:12 ` Pádraig Brady
2025-09-30 21:14 ` Bernhard Voelker
2025-09-30 13:23 ` Rob Landley
2025-09-30 13:35 ` G. Branden Robinson
2025-09-30 19:57 ` Arsen Arsenović
2025-09-30 20:55 ` G. Branden Robinson
2025-10-01 13:21 ` Arsen Arsenović
2025-10-01 19:37 ` Rob Landley
2025-10-02 18:46 ` Arsen Arsenović
2025-10-02 20:48 ` G. Branden Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sege1q8l.fsf@hippogriff \
--to=michael@greenberg.science \
--cc=P@draigbrady.com \
--cc=alx@kernel.org \
--cc=collin.funk1@gmail.com \
--cc=coreutils@gnu.org \
--cc=linux-man@vger.kernel.org \
--cc=williambader@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox