From: "Anthony J. Bentley" <anthony@cathet.us>
To: discuss@mdocml.bsd.lv
Subject: \u and \d
Date: Thu, 5 Dec 2013 23:58:55 -0700 [thread overview]
Message-ID: <CAFRrxyk1ku3v_kUqO55=s16FE1tLx8MkRwzNx1feVpkoUsy=Yg@mail.gmail.com> (raw)
\utest\d
Displays "test" in groff. In mandoc, it displays "utestd". I have no
idea what special formatting these escapes are meant to trigger (maybe
superscripts via 'u'p and 'd'own?), but they should be at least
ignored if they aren't implemented.
An example appears in pdf2djvu.1, generated from this (yes, more Docbook crap):
https://code.google.com/p/pdf2djvu/source/browse/doc/pdf2djvu.xml
It has some sort of footnotes system, such that this:
<ulink url='http://code.google.com/p/pdf2djvu/issues/'>the issue tracker</ulink>
generates this:
\m[blue]\fBthe issue tracker\fR\m[]\&\s-2\u[5]\d\s+2\&
--
Anthony J. Bentley
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2013-12-06 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 6:58 Anthony J. Bentley [this message]
2013-12-25 23:04 ` 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='CAFRrxyk1ku3v_kUqO55=s16FE1tLx8MkRwzNx1feVpkoUsy=Yg@mail.gmail.com' \
--to=anthony@cathet.us \
--cc=discuss@mdocml.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).