From: Thomas Klausner <wiz@NetBSD.org>
Subject: Re: pod2mdoc, docbook2mdoc
Date: Fri, 4 Apr 2014 00:06:32 +0200 [thread overview]
Message-ID: <20140403220632.GC20391@danbala.tuwien.ac.at> (raw)
On Thu, Apr 03, 2014 at 03:53:02PM +0200, Ingo Schwarze wrote:
> Thomas, you are already aiming high.
> All your suggestions definitely make sense, but
> they are beyond what the current state-of-the-art tools can do.
> Eric S. Raymond basically says that it took
> him a decade to get there, and he calls it very difficult.
A few years ago when I last tried doclifter I wasn't very impressed,
and your comparison today doesn't impress me much either...
Thanks for that comparison, btw!
> Which doesn't mean that Kristaps can't do better in a few days,
> but... well... ESR isn't exactly known for stupidity in the
> free software world, either, so bear with Kristaps. :)
I hope I wasn't misunderstood:
Kristaps, you're doing great!
I didn't mean to put you down in any way.
> No, it should not. The *.pod suffix just means "plain old documentation",
> that can be any section, even 3p - though 1, 3, 5, 7, 8 are maybe more
> likely than 3p because most Perlmodule docs are embedded in the *.pm.
> Anyway, you shouldn't conclude anything from a *.pod filename.
So worst-case we could tell pod2man with a flag which section the man
page belongs to.
To unsubscribe send an email to firstname.lastname@example.org
next prev parent reply other threads:[~2014-04-03 22:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20140330email@example.com>
2014-03-30 18:23 ` Kristaps Dzonsons
2014-03-31 9:09 ` Thomas Klausner
2014-03-31 10:30 ` Kristaps Dzonsons
2014-03-31 16:13 ` Ingo Schwarze
2014-03-31 19:40 ` Kristaps Dzonsons
2014-03-31 20:57 ` Ingo Schwarze
2014-03-31 21:30 ` Thomas Klausner
2014-03-31 21:54 ` Kristaps Dzonsons
2014-03-31 22:21 ` Ingo Schwarze
2014-03-31 22:31 ` Thomas Klausner
2014-04-03 12:02 ` Kristaps Dzonsons
2014-04-03 12:17 ` Thomas Klausner
2014-04-03 12:33 ` Kristaps Dzonsons
2014-04-03 13:53 ` Ingo Schwarze
2014-04-03 16:51 ` Kristaps Dzonsons
2014-04-03 22:06 ` Thomas Klausner [this message]
2014-04-04 13:43 ` Kristaps Dzonsons
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).