1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
<page xmlns="http://www.gnome.org/~shaunm/mallard"
type="guide"
id="mal_inline">
<info>
<link type="guide" xref="spec"/>
<version number="0.1" date="2009-04-16" status="review"/>
<credit type="author">
<name>Shaun McCance</name>
<email>shaunm@gnome.org</email>
</credit>
<copyright>
<year>2009</year>
<name>Shaun McCance</name>
</copyright>
<include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude" />
<desc>Rich semantic elements for marking up inline content.</desc>
</info>
<title>Inline Elements</title>
<synopsis><code mime="application/relax-ng-compact-syntax">
mal_inline = mixed {
<link xref="mal_inline_app">mal_inline_app</link> *,
<link xref="mal_inline_cmd">mal_inline_cmd</link> *,
<link xref="mal_inline_code">mal_inline_code</link> *,
<link xref="mal_inline_em">mal_inline_em</link> *,
<link xref="mal_inline_file">mal_inline_file</link> *,
<link xref="mal_inline_gui">mal_inline_gui</link> *,
<link xref="mal_inline_guiseq">mal_inline_guiseq</link> *,
<link xref="mal_inline_input">mal_inline_input</link> *,
<link xref="mal_inline_key">mal_inline_key</link> *,
<link xref="mal_inline_keyseq">mal_inline_keyseq</link> *,
<link xref="mal_inline_link">mal_inline_link</link> *,
<link xref="mal_inline_media">mal_inline_media</link> *,
<link xref="mal_inline_output">mal_inline_output</link> *,
<link xref="mal_inline_span">mal_inline_span</link> *,
<link xref="mal_inline_sys">mal_inline_sys</link> *,
<link xref="mal_inline_var">mal_inline_var</link> *,
element * - (mal:* | local:*) { mal_inline } *
}
</code></synopsis>
<p>Mallard provides a small but rich set of semantic inline elements.
The elements provided are culled from first-hand experience with software
documentation and other document formats. The inline elements defined in
this specification will serve most software documentation writers' needs
well.</p>
<p>Authors, editors, or other content producers sometimes need to supply
richer information in their documents. While this information may not
be conveyed by display tools, it may be used for various internal tracking
purposes. Mallard allows elements to be extended with attributes from
external namespaces. See <link xref="mal_external"/> for more
information.</p>
<p>Furthermore, Mallard allows elements from external namespaces to be
used in any inline context. See <link xref="#processing"/> below for
more information.</p>
<!-- BEGIN elements -->
<section id="elements" style="2column">
<info>
<title type="link">Inline Elements</title>
</info>
<title>Elements</title>
</section>
<!-- END elements -->
<!-- BEGIN processing -->
<section id="processing">
<info>
<title type="link">Inline Processing Instructions</title>
</info>
<title>Processing Expectations</title>
<p>Inline elements occur within block elements or other inline elements.
Mallard never allows block elements within inline elements. Inline elements
should never introduce a line break in the rendered output.</p>
<p>Different inline elements may introduce different styling effects, such
as font variations, text and background colors, and backgrounds. Generally,
if a styling effect is set for a particular element, it is in effect for all
descendant elements, unless explicitly overridden.</p>
<p>Mallard allows elements from external namespaces to be used in any inline
context. Processing tools may have special behavior for particular elements
they understand. Otherwise, an unknown inline element should be processed
as if it were replaced by its child content.</p>
</section>
<!-- END processing -->
</page>
|
