From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: pod2mdoc, docbook2mdoc
Date: Thu, 03 Apr 2014 14:02:41 +0200 [thread overview]
Message-ID: <533D4DE1.4030304@bsd.lv> (raw)
In-Reply-To: <20140331223147.GA17640@danbala.tuwien.ac.at>
>> Oh, indeed, the NetBSD base system does not contain Perl, right?
>> So you can't easily run pod2man(1) during the build?
>> I didn't think about that because in OpenBSD, we do just that...
>
> Yes, that's right.
> After import, pod2man is run manually once.
> I'm not very happy about the output and expect better from Kristaps :)
Thomas,
I suggest you check out the latest version... run as:
pod2mdoc foo.pm | mandoc
The output is much nicer than pod2man in the same way. Lots more
semantic content as mentioned in the "Smarts" subsection of the manual.
Most visibly, since the SYNOPSIS is now rendered with Nm, Oo/Oc, Ar,
and Fl, mandoc can properly format sections.
I specifically used the SSL manpages and Perl distribution as a basis.
Best,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-04-03 12:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20140330-202333-+022.64-1@spamfilter.osbf.lua>
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 [this message]
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
2014-04-04 13:43 ` Kristaps Dzonsons
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=533D4DE1.4030304@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@mdocml.bsd.lv \
/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;
as well as URLs for NNTP newsgroup(s).