From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: docbook2mdoc: treat <sect3> and <sect4> like <section>
Date: Tue, 16 Apr 2019 16:20:24 -0500 (EST) [thread overview]
Message-ID: <e3fdf133027c2dda@fantadrom.bsd.lv> (raw)
Log Message:
-----------
treat <sect3> and <sect4> like <section>
Modified Files:
--------------
docbook2mdoc:
parse.c
Revision Data
-------------
Index: parse.c
===================================================================
RCS file: /home/cvs/mdocml/docbook2mdoc/parse.c,v
retrieving revision 1.45
retrieving revision 1.46
diff -Lparse.c -Lparse.c -u -p -r1.45 -r1.46
--- parse.c
+++ parse.c
@@ -112,6 +112,8 @@ static const struct alias aliases[] = {
{ "secondary", NODE_DELETE },
{ "sect1", NODE_SECTION },
{ "sect2", NODE_SECTION },
+ { "sect3", NODE_SECTION },
+ { "sect4", NODE_SECTION },
{ "sgmltag", NODE_MARKUP },
{ "simpara", NODE_PARA },
{ "structfield", NODE_PARAMETER },
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2019-04-16 21:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e3fdf133027c2dda@fantadrom.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@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).