From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: docbook2mdoc: update links to the DocBook website and fix a typo in a
Date: Fri, 8 Mar 2019 05:13:42 -0500 (EST) [thread overview]
Message-ID: <e3f1862a87027278@fantadrom.bsd.lv> (raw)
Log Message:
-----------
update links to the DocBook website and fix a typo in a function name
Modified Files:
--------------
docbook2mdoc:
README
Revision Data
-------------
Index: README
===================================================================
RCS file: /home/cvs/mdocml/docbook2mdoc/README,v
retrieving revision 1.1
retrieving revision 1.2
diff -LREADME -LREADME -u -p -r1.1 -r1.2
--- README
+++ README
@@ -2,9 +2,15 @@ $Id$
Here's a quick note on how to add new DocBook elements.
-First, look up the element in the DocBook reference. For element <foo>, this is usually:
+First, look up the element in the DocBook reference.
+For element <foo>, this is usually:
-http://docbook.org/tdg51/en/html/foo.html
+ https://tdg.docbook.org/tdg/5.1/foo.html
+
+Some elements are no longer defined in DocBook 5.
+For these, you will have to look at 4.5 documentation instead:
+
+ https://tdg.docbook.org/tdg/4.5/foo.html
Add the alpha-ordered node (NODE_FOO) to extern.h.
@@ -30,6 +36,6 @@ Now the hard work is finished!
Next, add the name and whether it admits text to docbook2mdoc.c's
"nodes" structure array.
-Finally, modify print_pnode() with your new entry. Use similar nodes as
+Finally, modify pnode_print() with your new entry. Use similar nodes as
a reference. (NOTE: if it's an inline like, say, NODE_EMPHASIS, then
remember to add the node to the postfix switch statement!)
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2019-03-08 10:13 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=e3f1862a87027278@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).