From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: Re: Is there any reason not to use <EM> for items emphasized with .Em?
Date: Wed, 13 Aug 2014 03:44:39 +0200 [thread overview]
Message-ID: <20140813014439.GA20283@britannica.bec.de> (raw)
In-Reply-To: <01237D5A-9F46-4047-83BF-A98CAB0C16E1@alum.mit.edu>
On Tue, Aug 12, 2014 at 03:44:07PM -0700, Guy Harris wrote:
> Is there any reason not to use that tag for text emphasized with .Em?
I like the idea, but I wonder if we should just drop the manual rules.
Joerg
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-08-13 1:44 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
2014-08-13 1:44 ` Joerg Sonnenberger [this message]
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=20140813014439.GA20283@britannica.bec.de \
--to=joerg@britannica.bec.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).