From: Stephen Gregoratto <dev@sgregoratto.me>
To: tech@mandoc.bsd.lv
Subject: [PATCH docbook2mdoc] Add NODE_CONTRIB, NODE_PRODUCTNAME
Date: Wed, 27 Mar 2019 14:52:24 +1100 [thread overview]
Message-ID: <20190327035224.7eyuctlnbt67pu5r@BlackBox> (raw)
Here are some nodes I found in the wild.
Technically <productname> is used to markup text as
copyright/trademark/registered, but the Systemd and GTK manuals use it
to set the "source" argument of TH in man(7). We have no need for it.
<contrib> is a bit odd case. It classifies an <author>'s contributions
to the program/manual/code etc. Here's an example from GTK:
<authorgroup>
<author>
<contrib>Developer</contrib>
<firstname>Matthias</firstname>
<surname>Clasen</surname>
</author>
</authorgroup>
I'm setting it to be skipped for now, but if we ever start recording
<author>s we could probably include this.
--
Stephen Gregoratto
PGP: 3FC6 3D0E 2801 C348 1C44 2D34 A80C 0F8E 8BAB EC8B
Index: node.h
===================================================================
RCS file: /cvs/docbook2mdoc/node.h,v
retrieving revision 1.4
diff -u -p -r1.4 node.h
--- node.h 26 Mar 2019 22:39:33 -0000 1.4
+++ node.h 27 Mar 2019 03:28:02 -0000
@@ -46,6 +46,7 @@ enum nodeid {
NODE_COLSPEC,
NODE_COMMAND,
NODE_CONSTANT,
+ NODE_CONTRIB,
NODE_COPYRIGHT,
NODE_DATE,
NODE_EDITOR,
@@ -98,6 +99,7 @@ enum nodeid {
NODE_PARAMETER,
NODE_PERSONNAME,
NODE_PREFACE,
+ NODE_PRODUCTNAME,
NODE_PROGRAMLISTING,
NODE_PROMPT,
NODE_QUOTE,
Index: parse.c
===================================================================
RCS file: /cvs/docbook2mdoc/parse.c,v
retrieving revision 1.4
diff -u -p -r1.4 parse.c
--- parse.c 26 Mar 2019 22:39:33 -0000 1.4
+++ parse.c 27 Mar 2019 03:28:02 -0000
@@ -64,6 +64,7 @@ static const struct element elements[] =
{ "citetitle", NODE_CITETITLE },
{ "cmdsynopsis", NODE_CMDSYNOPSIS },
{ "code", NODE_CODE },
+ { "contrib", NODE_CONTRIB },
{ "colspec", NODE_COLSPEC },
{ "command", NODE_COMMAND },
{ "constant", NODE_CONSTANT },
@@ -125,6 +126,7 @@ static const struct element elements[] =
{ "phrase", NODE_IGNORE },
{ "preface", NODE_PREFACE },
{ "primary", NODE_DELETE },
+ { "productname", NODE_PRODUCTNAME },
{ "programlisting", NODE_PROGRAMLISTING },
{ "prompt", NODE_PROMPT },
{ "quote", NODE_QUOTE },
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2019-03-27 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 3:52 Stephen Gregoratto [this message]
2019-03-28 17:19 ` Ingo Schwarze
2019-03-28 20:53 ` 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=20190327035224.7eyuctlnbt67pu5r@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).