tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Anthony J. Bentley" <anthony@cathet.us>
To: Ingo Schwarze <schwarze@usta.de>
Cc: tech@mdocml.bsd.lv, Guy Harris <guy@alum.mit.edu>
Subject: Re: Is there any reason not to use <EM> for items emphasized with .Em?
Date: Wed, 13 Aug 2014 09:17:55 -0600	[thread overview]
Message-ID: <16640.1407943075@cathet.us> (raw)
In-Reply-To: <20140813145148.GA26534@iris.usta.de>

Hi Ingo,

I agree with your analysis. However:

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."

<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."

http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#the-var-element
http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#the-samp-element
http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#the-kbd-element

-- 
Anthony J. Bentley

--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2014-08-13 15:18 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 [this message]
2014-08-13 17:49         ` Ingo Schwarze
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=16640.1407943075@cathet.us \
    --to=anthony@cathet.us \
    --cc=guy@alum.mit.edu \
    --cc=schwarze@usta.de \
    --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).