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
|
<refentry id="msg.element">
<?dbhtml filename="msg.html"?>
<refentryinfo>
<pubdate>$Date$</pubdate>
<releaseinfo>$Revision$</releaseinfo>
</refentryinfo>
<refmeta>
<indexterm><primary>elements</primary>
<secondary>msg</secondary></indexterm>
<refentrytitle>msg</refentrytitle>
<refmiscinfo>Element</refmiscinfo>
</refmeta>
<refnamediv>
<refname>msg</refname>
<refpurpose>&msg.purpose;</refpurpose>
</refnamediv>
&msg.synopsis.gen;
<refsect1 condition='ref.description'><title>Description</title>
<para>
In a <sgmltag>MsgSet</sgmltag>, each <sgmltag>MsgEntry</sgmltag> contains at least
one <sgmltag>Msg</sgmltag>. A <sgmltag>Msg</sgmltag> consists of a main message
(<sgmltag>MsgMain</sgmltag>),
and optionally one or more submessages (<sgmltag>MsgSub</sgmltag>)
or related messages (<sgmltag>MsgRel</sgmltag>).
</para>
<para>
Additional information or explanation for the message is contained
in the siblings of <sgmltag>Msg</sgmltag> within the <sgmltag>MsgEntry</sgmltag>.
</para>
<para>See <sgmltag>MsgSet</sgmltag>.</para>
<refsect2><title>Processing expectations</title>
<para>
&format.block; &format.csuppress;
</para>
<para>
On the whole, the semantics of <sgmltag>MsgSet</sgmltag>
are not clearly defined.
</para>
</refsect2>
&msg.parents.gen;
&msg.children.gen;
</refsect1>
<refsect1><title>Examples</title>
&msg.example.seealso.gen;
</refsect1>
</refentry>
|
