aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/html.c
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2014-08-13 15:25:22 +0000
committerIngo Schwarze <schwarze@openbsd.org>2014-08-13 15:25:22 +0000
commit08b7f86267663883d71e98c502652ec334c232bc (patch)
tree0abce60889668c8d52f51d9f27148ca85a77beec /html.c
parentfaf800341f0f487ab0edd954fb2a6e0eddb2db96 (diff)
downloadmandoc-08b7f86267663883d71e98c502652ec334c232bc.tar.gz
mandoc-08b7f86267663883d71e98c502652ec334c232bc.tar.zst
mandoc-08b7f86267663883d71e98c502652ec334c232bc.zip
Use <em> for .Em and .Bf -emphasis.
The vast majority of .Em in real-world manuals is stress emphasis, for which <em> is the correct markup. Admittedly, there are some instances of .Em usage for alternate quality, for which <i> would be a better match. Most of these are technical terms that neither allow semantic markup nor are keywords - for the latter, .Sy would be preferable. A typical example is that the shell breaks input into .Em words . Alternate voice or mood, which would also require <i>, is almost absent from manuals. We cannot satisfy both stress emphasis and alternate quality, so pick the one that fits more often and looks less wrong when off. Patch from Guy Harris <guy at alum dot mit dot edu>. ok joerg@ bentley@
Diffstat (limited to 'html.c')
-rw-r--r--html.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/html.c b/html.c
index e7da3ad3..0fd6f04d 100644
--- a/html.c
+++ b/html.c
@@ -1,4 +1,4 @@
-/* $Id: html.c,v 1.160 2014/08/10 23:54:41 schwarze Exp $ */
+/* $Id: html.c,v 1.161 2014/08/13 15:25:22 schwarze Exp $ */
/*
* Copyright (c) 2008, 2009, 2010, 2011 Kristaps Dzonsons <kristaps@bsd.lv>
* Copyright (c) 2011, 2012, 2013, 2014 Ingo Schwarze <schwarze@openbsd.org>
@@ -74,6 +74,7 @@ static const struct htmldata htmltags[TAG_MAX] = {
{"i", 0 }, /* TAG_I */
{"code", 0 }, /* TAG_CODE */
{"small", 0 }, /* TAG_SMALL */
+ {"em", 0 }, /* TAG_EM */
};
static const char *const htmlattrs[ATTR_MAX] = {