From: josh@joshtriplett.org
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Documentation
Date: Wed, 5 Aug 2015 10:19:54 -0700 [thread overview]
Message-ID: <20150805171954.GB32266@cloud> (raw)
In-Reply-To: <55C242F4.7090005@gmail.com>
On Wed, Aug 05, 2015 at 07:08:04PM +0200, Michael Kerrisk (man-pages) wrote:
> From a man-pages point of view, the discussion of tooling is interesting.
> For some years now I've contemplated a switch from groff's man macros,
> since some people do not like to work with them (although the basics are
> pretty simple, IMO). If there was a concerted movement to Asciidoc or
> Markdown for kernel docs, I'd be willing to invest some effort in the
> feasibility of switching man-pages to the same format. I'm not
> knowledgeable in either of those tools, but at a first glance,
> Asciidoc seems more interesting, since it seems to embrace a wider
> variety of output formats, in particular, PDF and Linux man-page
> macros (and also TeX). It doesn't appear that Markdown can do that.
> I know even less about Sphinx, although its output capabilities,
> as described at http://sphinx-doc.org/index.html , seem interesting also.
I've seen multiple scripts to convert mdwn to groff for manual pages.
And once you have groff, you can typeset PDFs from that, right?
The biggest thing I've noticed about asciidoc is that it seems to be
incredibly *slow*. For all the projects I know of that use it, building
the documentation is by far the slowest part of the build process.
Honestly, groff isn't *that* hard to deal with.
- Josh Triplett
next prev parent reply other threads:[~2015-08-05 17:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 14:41 Jonathan Corbet
2015-08-02 7:07 ` Davidlohr Bueso
2015-08-03 13:35 ` Rafael J. Wysocki
2015-08-03 13:27 ` Konstantin Ryabitsev
2015-08-03 14:33 ` Jonathan Corbet
2015-08-03 20:45 ` Dmitry Torokhov
2015-08-04 10:59 ` Daniel Vetter
2015-08-04 0:52 ` Rafael J. Wysocki
2015-08-04 12:50 ` Laurent Pinchart
2015-08-04 13:03 ` Daniel Vetter
2015-08-04 14:28 ` Laurent Pinchart
2015-08-04 14:30 ` Daniel Vetter
2015-08-04 13:50 ` Dan Carpenter
2015-08-04 14:05 ` Geert Uytterhoeven
2015-08-04 14:29 ` Daniel Vetter
2015-08-04 14:30 ` Laurent Pinchart
2015-08-04 17:10 ` Geert Uytterhoeven
2015-08-04 14:42 ` Konstantin Ryabitsev
2015-08-04 18:21 ` Tim Bird
2015-08-04 21:00 ` Laurent Pinchart
2015-08-04 15:35 ` Mark Brown
2015-08-05 17:07 ` Michael Kerrisk (man-pages)
2015-08-04 17:24 ` Jonathan Corbet
2015-08-04 7:12 ` Michael Ellerman
2015-08-04 7:42 ` Marcel Holtmann
2015-08-04 8:33 ` Peter Huewe
2015-08-05 17:08 ` Michael Kerrisk (man-pages)
2015-08-05 17:19 ` josh [this message]
2015-08-05 17:21 ` Konstantin Ryabitsev
2015-08-04 12:54 ` Laurent Pinchart
2015-08-04 13:07 ` Daniel Vetter
2015-08-04 11:09 ` Daniel Vetter
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=20150805171954.GB32266@cloud \
--to=josh@joshtriplett.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mtk.manpages@gmail.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