1
<?xml version="1.0" encoding="utf-8"?>
2
<page xmlns="http://projectmallard.org/1.0/" type="topic" id="mal_inline_em">
5
<link type="guide" xref="mal_inline#elements"/>
7
<revision version="0.1" date="2008-12-16" status="review"/>
10
<name>Shaun McCance</name>
11
<email>shaunm@gnome.org</email>
12
<years>2008-2009</years>
15
<include xmlns="http://www.w3.org/2001/XInclude" href="legal.xml"/>
17
<desc>Emphasize important text.</desc>
20
<title>Emphasis</title>
22
<synopsis><code mime="application/relax-ng-compact-syntax">
23
mal_inline_em = element em {
24
<link xref="mal_attr_link">mal_attr_link</link> ?,
25
attribute style { xsd:NMTOKENS } ?,
26
attribute * - (mal:* | local:*) { text } *,
28
<link xref="mal_inline">mal_inline</link>
32
<p>Use the <code>em</code> element to emphasize text. You may use <code>em</code>
33
to stress certain words in a sentence. Do not use <code>em</code> to effect a
34
particular typographic style, since it may be rendered differently by different
40
<title>Anmerkungen</title>
42
<item><p>The <code>em</code> element can contain a mixture of text and
43
any <link xref="mal_inline">general inline elements</link>.</p></item>
45
<item><p>The <code>em</code> element can occur in any
46
general inline context, including inside most
47
<link xref="mal_inline">inline elements</link>, some
48
<link xref="mal_block#basic">basic block elements</link>, and certain
49
<link xref="mal_info">informational elements</link>.</p></item>
51
<item><p>The <code>em</code> element can link to other pages or documents.
52
See <link xref="mal_attr_link"/> for more information.</p></item>
54
<item><p>The <code>style</code> attribute takes a space-separated list of
55
style hints. Processing tools should adjust their behavior according to
56
those style hints they understand.</p></item>
58
<item><p>The <code>em</code> element can have attributes from external
59
namespaces. See <link xref="mal_external"/> for more information
60
on external-namespace attributes.</p></item>
66
<!-- BEGIN examples -->
67
<section id="examples">
68
<title>Beispiele</title>
70
<p>Use <code>em</code> to stress a word in a sentence:</p>
74
You should <em>never</em> run a graphical application as root.
76
<p>You should <em>never</em> run a graphical application as root.</p>
79
<p>Use <code>em</code> to mark the first occurance of a term:</p>
83
Note that <em>accelerators</em> are different from <em>mnemonics</em>.
85
<p>Note that <em>accelerators</em> are different from <em>mnemonics</em>.</p>
91
<!-- BEGIN processing -->
92
<section id="processing">
93
<title>Processing Expectations</title>
94
<p>Emphasized text is traditionally presented in an italic or oblique font.
95
Italic and oblique fonts stress a portion of text without making it stand
96
out. By contrast, bold text tends to draw the eye, which can be distracting
97
when reading long passages of text. In scripts without a distinction between
98
roman and italic type styles, it may still be possible to use an oblique font
99
or some other font variation. Bold text may be used if necessary.</p>
100
<p>Underlining should be avoided completely, since it hurts the legibility
101
of the text. This problem is especially pronounced in scripts which place
102
diacritical marks below the text. In these scripts, underlining can render
103
the text completely illegible.</p>
105
<!-- END processing -->
108
<!-- BEGIN comparison -->
109
<section id="comparison">
110
<title>Vergleich mit anderen Formaten</title>
111
<p>The <code>em</code> element is similar to the
112
<code href="http://www.docbook.org/tdg/en/html/emphasis.html">emphasis</code>
113
element in DocBook. Athough DocBook does not normatively specify a means of
114
controlling the presentation, most DocBook display tools allow writers to
115
set the <code>role</code> attribute to <code>bold</code> or <code>strong</code>
116
to specify bold text. No such recommendation is made for Mallard.</p>
118
<!-- END comparison -->
added
removed
doc/mallard/de/mal_inline_em.page
