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

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

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

<para>
<sgmltag>TertiaryIE</sgmltag> identifies a third-level word or
words in an <sgmltag>IndexEntry</sgmltag>.
</para>

<para>
In <sgmltag>IndexEntry</sgmltag>s, you can specify as many tertiary terms
that are necessary.  Secondary and tertiary terms can be mixed, following
the primary.
</para>

<refsect2><title>Processing expectations</title>
<para>
&format.block; <sgmltag>TertiaryIE</sgmltag>s occur below the 
<sgmltag>SecondaryIE</sgmltag>, and are usually aligned with each other and indented
from the secondary.
</para>
</refsect2>

<refsect2 role='fu' revision="4.0"><title>&FutureChanges;</title>
<para>
<!--do not index this occurance-->
&fu.interfacedefinition;
</para>
</refsect2>


&tertiaryie.parents.gen;
&tertiaryie.children.gen;
</refsect1>
<refsect1 condition='ref.elem.attrdesc'><title>Attributes</title>
<variablelist>
<varlistentry><term>linkends</term>
<listitem>
<para>
<sgmltag class="attribute">Linkends</sgmltag>, if used, points to the <sgmltag>IndexTerm</sgmltag>s indexed
by this entry.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&tertiaryie.seealso.gen;
</refsect1>

</refentry>

