From: "Anthony J. Bentley" <anthony@anjbe.name>
To: tech@mandoc.bsd.lv
Subject: docbook2mdoc(1) sometimes mishandles
Date: Mon, 20 May 2019 02:34:19 -0600 [thread overview]
Message-ID: <3491.1558341259@desktop.ajb.soy> (raw)
Hi,
From fonts.xml:
<sect3 id='Standard_Type1_fonts'>
<title>Standard Type 1 fonts</title>
docbook2mdoc turns this into:
.Pp
.Sy Standard Type\e1 fonts
It happens again near the end of the document:
<para>
The IETF RFC documents, available from a number of sites throughout
the world, often provide interesting information about character set
issues; see for example <ulink
url="https://datatracker.ietf.org/doc/rfc373/">RFC 373</ulink>.
</para>
becomes:
.Pp
The IETF RFC documents, available from a number of sites throughout
the world, often provide interesting information about character set
issues; see for example
.Lk https://datatracker.ietf.org/doc/rfc373/ "RFC\e373" .
--
Anthony J. Bentley
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2019-05-20 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 8:34 Anthony J. Bentley [this message]
2019-05-20 20:38 ` 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=3491.1558341259@desktop.ajb.soy \
--to=anthony@anjbe.name \
--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).