<refentry id="msgset.element">
<?dbhtml filename="msgset.html"?>
<refentryinfo>
<pubdate>$Date$</pubdate>
<releaseinfo>$Revision$</releaseinfo>
</refentryinfo>

<refmeta>
<indexterm><primary>elements</primary>
<secondary>msgset</secondary></indexterm>
<refentrytitle>msgset</refentrytitle>
<refmiscinfo>Element</refmiscinfo>
</refmeta>
<refnamediv>
<refname>msgset</refname>
<refpurpose>&msgset.purpose;</refpurpose>
</refnamediv>

&msgset.synopsis.gen;
<refsect1 condition='ref.description'><title>Description</title>

<para>
<sgmltag>MsgSet</sgmltag> is a complex structure designed to hold a detailed
set of messages, usually error messages.  In addition to the actual text
of each message, it can contain 
additional information about each message and the messages related to it.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.block;
</para>
<para>
On the whole, the semantics of <sgmltag>MsgSet</sgmltag>
are not clearly defined.
</para>
</refsect2>



&msgset.parents.gen;
&msgset.children.gen;
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&msgset.seealso.gen;
</refsect1>
<refsect1><title>Examples</title>

<informalexample role="example-source">
<programlisting>&msgset.example.1.txt;</programlisting>
</informalexample>

<anchor id="ex.os.msgset.1" role="HACK-ex.out.start"/>
&msgset.example.1.gen;
<anchor id="ex.oe.msgset.1" role="HACK-ex.out.end"/>

&msgset.example.seealso.gen;
</refsect1>
</refentry>

