From: Kristaps Dzonsons <firstname.lastname@example.org>
To: Ingo Schwarze <email@example.com>
Subject: Re: pod2mdoc, docbook2mdoc
Date: Mon, 31 Mar 2014 21:40:10 +0200 [thread overview]
Message-ID: <5339C49A.firstname.lastname@example.org> (raw)
> I wouldn't worry too much about that. The version number 0.0.5
> is telling enough, and the package description can say a few words
> too. So i see no big risk there, but possible benefit allowing
> cleaner packaging, installation and deinstallation of experimental
Thank you for your input! This looks logical to me. I'll drop a note
here when I bump versions in a meaningful way--does that work? Note for
those with commit access that the modules are in
/usr/vhosts/mdocml.bsd.lv/pod2mdoc and so. (The commit hook in CVSROOT
should probably be updated to mail commits on the new modules...)
>> 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.
> Indeed. As far as i can see, the biggest problem right now is that
> it usually exits in the middle of each processed file, rendering
> merely the beginning. To be usable, it has to become more resilient.
Yes. This is because I don't support a huge set of docbook elements
yet--and the parser exits when it encounters an unknown one to spur me
to add as many new ones as possible. My plan (as you've noted below) is
to start by having it accept all of doclifter's DocBook, then focus on
the rest, possibly relaxing the parser to accept unknown nodes if we get
Fortunately, it's easy to add new nodes to docbook2mdoc! They need an
entry in extern.h, then the rules of parenting (this is the most
annoying part--both children and parents need to be added in) in
rules.c, then a handler in pnode_print(). Most handler types have
already been implemented, so it's just putting together the blocks and
going by example. Attributes work more or less the same way.
> At first sight, it seems that the "ps->stop = 1;" in the
> function xml_elem_start() cause the problem, but i didn't
> try to come up with a fix yet.
> cvs.1.xml:33:6: unknown node "indexterm"
> lynx.1.xml:83:0: unknown node "literallayout"
> sqlite3.1.xml:108:0: unknown node "markup"
This is by design--it just means that I need to add a NODE_INDEXTERM,
etc. As mentioned, I'm going to start with doclifter's nodes.
>> 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?
> A good corpus of test input would be the man(7) manuals in OpenBSD
> base, imho. As far as these are POD input, they are good testing
> candidates for pod2mdoc; i consider the test chain POD -> pod2man ->
> man(7) -> doclifter -> DocBook-XML -> docbook2mdoc mostly useless.
> As far as they are real man(7), not from POD, they are good testing
> candidates for docbook2mdoc, i.e. using the testing chain
> man(7) -> doclifter -> DocBook-XML -> docbook2mdoc -> mdoc(7).
> At least at first, i think the main use for docbook2mdoc will
> be as a postprocessor for doclifter, so getting it to handle
> the subset of DocBook-XML produced by doclifter is the second
> most useful step to take after preventing it from exiting
> prematurely (see above).
> In any case, docbook2mdoc seems much more useful than pod2mdoc,
> at least in a short-term perspective.
My general thought on pod2mdoc was to avoid invoking perl(1) just to run
pod2man(1) in the normal chain of looking at POD documents. I also
thought that, with a few more pod2mdoc smarts, we'll be able to deeply
mine those documents with mandocdb. From what I understand, they're
kinda opaque right now.
To unsubscribe send an email to email@example.com
next prev parent reply other threads:[~2014-03-31 19:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20140330firstname.lastname@example.org>
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 [this message]
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
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).