diff options
| author | Ingo Schwarze <schwarze@openbsd.org> | 2014-08-13 15:25:22 +0000 |
|---|---|---|
| committer | Ingo Schwarze <schwarze@openbsd.org> | 2014-08-13 15:25:22 +0000 |
| commit | ad2b1e6bad9b1abd3a86026b76e5fb100aaca2e4 (patch) | |
| tree | bc09f80ed339586fd911f537102268c99ff9c3f9 /style.css | |
| parent | 945af9fb48f5e5be490e4cbfdb654fad24f705aa (diff) | |
| download | mandoc-ad2b1e6bad9b1abd3a86026b76e5fb100aaca2e4.tar.gz | |
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 'style.css')
| -rw-r--r-- | style.css | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -34,7 +34,7 @@ td.head-rtitle { width: 10%; text-align: right; } /* Document header: right-titl /* General font modes. */ i { } /* Italic: BI, IB, I, (implicit). */ -.emph { font-style: italic; font-weight: normal; } /* Emphasis: Em, Bl -emphasis. */ +em { font-style: italic; font-weight: normal; } /* Emphasis: Em, Bl -emphasis. */ b { } /* Bold: SB, BI, IB, BR, RB, B, (implicit). */ .symb { font-style: normal; font-weight: bold; } /* Symbolic: Sy, Ms, Bf -symbolic. */ small { } /* Small: SB, SM. */ |