From: Stephen Gregoratto <dev@sgregoratto.me>
To: tech@mandoc.bsd.lv
Subject: [docbook2mdoc] Treat <info> as <refentryinfo>
Date: Wed, 24 Apr 2019 01:01:47 +1000 [thread overview]
Message-ID: <20190423150147.ylbr34gnsdb6txda@BlackBox> (raw)
In DocBook 5.x, <refentryinfo> morphed into <info>, but docbook2mdoc
does not format them the same way. On my files, info is printed at the
top before NAME. I tried aliasing info to refentry info but the output
became mangled, with PREFACE's and mutiple SYNOPSIS' inserted.
--
Stephen Gregoratto
PGP: 3FC6 3D0E 2801 C348 1C44 2D34 A80C 0F8E 8BAB EC8B
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2019-04-23 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 15:01 Stephen Gregoratto [this message]
2019-04-23 15:04 ` Stephen Gregoratto
2019-04-23 22:33 ` Ingo Schwarze
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=20190423150147.ylbr34gnsdb6txda@BlackBox \
--to=dev@sgregoratto.me \
--cc=tech@mandoc.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).