From: Stephen Gregoratto <dev@sgregoratto.me>
To: tech@mandoc.bsd.lv
Subject: [PATCH docbook2mdoc] Add NODE_SIMPARA
Date: Sat, 6 Apr 2019 20:33:40 +1100 [thread overview]
Message-ID: <20190406093327.66armzmidymuzi7j@BlackBox> (raw)
From the spec:
> A simpara is a "simple paragraph," one that may contain only
> character data and inline elements.
<simpara>
Just the text, ma'am.
</simpara>
Since we don't care about validation, treat it the same as <para>.
Index: docbook2mdoc.c
===================================================================
RCS file: /cvs/docbook2mdoc/docbook2mdoc.c,v
retrieving revision 1.91
diff -u -p -r1.91 docbook2mdoc.c
--- docbook2mdoc.c 3 Apr 2019 18:52:40 -0000 1.91
+++ docbook2mdoc.c 6 Apr 2019 09:24:49 -0000
@@ -764,6 +764,7 @@ pnode_print(struct format *p, struct pno
pnode_printlist(p, pn);
break;
case NODE_PARA:
+ case NODE_SIMPARA:
pnode_printpara(p, pn);
break;
case NODE_PARAMDEF:
Index: node.h
===================================================================
RCS file: /cvs/docbook2mdoc/node.h,v
retrieving revision 1.9
diff -u -p -r1.9 node.h
--- node.h 3 Apr 2019 17:53:02 -0000 1.9
+++ node.h 6 Apr 2019 09:24:49 -0000
@@ -121,6 +121,7 @@ enum nodeid {
NODE_SCREEN,
NODE_SECTION,
NODE_SGMLTAG,
+ NODE_SIMPARA,
NODE_SIMPLELIST,
NODE_SPANSPEC,
NODE_SUBTITLE,
Index: parse.c
===================================================================
RCS file: /cvs/docbook2mdoc/parse.c,v
retrieving revision 1.14
diff -u -p -r1.14 parse.c
--- parse.c 5 Apr 2019 14:37:36 -0000 1.14
+++ parse.c 6 Apr 2019 09:24:49 -0000
@@ -170,6 +170,7 @@ static const struct element elements[] =
{ "sect2", NODE_SECTION },
{ "section", NODE_SECTION },
{ "sgmltag", NODE_SGMLTAG },
+ { "simpara", NODE_SIMPARA },
{ "simplelist", NODE_SIMPLELIST },
{ "spanspec", NODE_SPANSPEC },
{ "structfield", NODE_PARAMETER },
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2019-04-06 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 9:33 Stephen Gregoratto [this message]
2019-04-06 13:51 ` 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=20190406093327.66armzmidymuzi7j@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).