From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: pod2mdoc, docbook2mdoc
Date: Sun, 30 Mar 2014 20:23:05 +0200 [thread overview]
Message-ID: <53386109.9000504@bsd.lv> (raw)
Hiya folks,
Long story short: any Perl POD or DocBook people out there?
In recent chatter on groff's mailing list, there's been talk about
manpages. For reasons (maybe) clear to anybody reading these, I thought
I'd write some tools that might help people start putting their weight
behind mdoc.
To wit,
http://mdocml.bsd.lv/pod2mdoc
http://mdocml.bsd.lv/docbook2mdoc
The second requires libexpat (for the XML parsing), but beyond that,
they're both standalone utilities. No Perl. No weird... XSLT...
jade... whatever things.
I've little time these days, so I thought maybe somebody would be
interested in delving into these utilities and seeing how they stack up
against the real world. There's a lot of meat to both.
pod2mdoc does a decent job given the many POD manuals out there, but
could use more "semantic suck". (E.g., pod2man is able to "recognise"
functions--that'd be swell for us, too. The SYNOPSIS is a horror, too.)
docbook2mdoc is a larger project just because docbook has so many
elements. So mechanically larger, not larger in terms of brains. It
also needs a bit of "doclifter desucking", as many docbook manuals I've
seen are from doclifter, which mangles some things (e.g., Xr).
Anybody interested? Bueller? Bueller?
Best,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2014-03-30 18:23 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 [this message]
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
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=53386109.9000504@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).