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

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

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

<para>
A <sgmltag>SetIndex</sgmltag> contains the formatted index of a complete
<sgmltag>Set</sgmltag> of <sgmltag>Book</sgmltag>s.
An index may begin with introductory material, followed by
any number of <sgmltag>IndexEntry</sgmltag>s or <sgmltag>IndexDiv</sgmltag>s.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.block; An <sgmltag>Index</sgmltag> in a <sgmltag>Set</sgmltag>
usually causes a forced page break in print media.
</para>

<para>
In many processing systems, indexes are generated automatically or 
semiautomatically and never appear instantiated as DocBook markup.
</para>
</refsect2>



&setindex.parents.gen;
&setindex.children.gen;
</refsect1>
<refsect1><title>Examples</title>

<para>
See <sgmltag>Index</sgmltag>.
</para>


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

