From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: pod2mdoc, docbook2mdoc
Date: Mon, 31 Mar 2014 12:30:17 +0200 [thread overview]
Message-ID: <533943B9.5080901@bsd.lv> (raw)
In-Reply-To: <20140331090912.GW26456@danbala.tuwien.ac.at>
> This sounds interesting. To make it easier for pkgsrc people to do
> that, I've just added packages for both of them: textproc/pod2mdoc and
> textproc/docbook2mdoc.
Thomas and Anthony,
Thank you for doing this! Though I worry... is this not moving too
fast? These tools are fresh--real fresh--and moving fast. Is it not too
soon for committing to a port? pod2mdoc works over all the POD I found
(not being a Perl junkie, however, I just used what's in the Perl
distribution), but docbook2mdoc still needs a lot of work. Fact is, I
just don't know the "real world" landscape of ports using docbook (or
POD, for that matter). Would it not be better to have somebody using
(or porting) POD or DocBook systems to break them in before putting them
out for general consumption? Thoughts?
Best,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-03-31 10:30 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 [this message]
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
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=533943B9.5080901@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).