From: Ingo Schwarze <schwarze@usta.de>
To: "Anthony J. Bentley" <anthony@cathet.us>
Cc: tech@mdocml.bsd.lv
Subject: Re: Is there any reason not to use <EM> for items emphasized with .Em?
Date: Wed, 13 Aug 2014 19:49:59 +0200 [thread overview]
Message-ID: <20140813174959.GF26534@iris.usta.de> (raw)
In-Reply-To: <16640.1407943075@cathet.us>
Hi Anthony,
Anthony J. Bentley wrote on Wed, Aug 13, 2014 at 09:17:55AM -0600:
> Ingo Schwarze writes:
>> So i think we should go for the following mappings:
>> ...
>> - .Li Ql .Dl .Bd -literal -> <code>
> This may be the best choice. Some alternatives to consider (if not for
> these then maybe for some of the more semantic macros):
>
> <var>: "The var element represents a variable."
That's too specific for the macros mentioned above,
but i added this note to the TODO file:
- consider whether <var> can be used for Ar Dv Er Ev Fa Va.
from bentley@ Wed, 13 Aug 2014 09:17:55 -0600
> <samp>: "The samp element represents sample or quoted output from another
> program or computing system."
>
> <kbd>: "The kbd element represents user input (typically keyboard input,
> although it may also be used to represent other input, such as voice
> commands."
There are no macros specific enough for that, the general recommendation
is to use literal mode for such content.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-08-13 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 22:44 Guy Harris
2014-08-13 1:15 ` Ingo Schwarze
2014-08-13 2:06 ` Anthony J. Bentley
2014-08-13 14:51 ` Ingo Schwarze
2014-08-13 15:17 ` Anthony J. Bentley
2014-08-13 17:49 ` Ingo Schwarze [this message]
2014-08-13 1:44 ` Joerg Sonnenberger
2014-08-13 15:30 ` Ingo Schwarze
2014-08-13 17:20 ` Ingo Schwarze
2014-08-13 18:53 ` Guy Harris
2014-08-13 23:24 ` Kristaps Dzonsons
2014-08-14 0:46 ` Ingo Schwarze
-- strict thread matches above, loose matches on Subject: below --
2012-12-21 0:30 Guy Harris
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=20140813174959.GF26534@iris.usta.de \
--to=schwarze@usta.de \
--cc=anthony@cathet.us \
--cc=tech@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).