Skip to main content
Version: DocBook V4.5

see

see — Part of an index term directing the reader instead to another entry in the index

Synopsis

Mixed Content Model

see ::=
(#PCDATA|footnoteref|xref|biblioref|abbrev|acronym|citation|
citerefentry|citetitle|citebiblioid|emphasis|firstterm|
foreignphrase|glossterm|termdef|footnote|phrase|orgname|quote|
trademark|wordasword|personname|link|olink|ulink|action|
application|classname|methodname|interfacename|exceptionname|
ooclass|oointerface|ooexception|package|command|computeroutput|
database|email|envar|errorcode|errorname|errortype|errortext|
filename|function|guibutton|guiicon|guilabel|guimenu|guimenuitem|
guisubmenu|hardware|interface|keycap|keycode|keycombo|keysym|
literal|code|constant|markup|medialabel|menuchoice|mousebutton|
option|optional|parameter|prompt|property|replaceable|
returnvalue|sgmltag|structfield|structname|symbol|systemitem|uri|
token|type|userinput|varname|nonterminal|anchor|author|
authorinitials|corpauthor|corpcredit|modespec|othercredit|
productname|productnumber|revhistory|remark|subscript|
superscript|inlinegraphic|inlinemediaobject)*

Attributes

Common attributes

Description

The use of See in an IndexTerm indicates that the reader should be directed elsewhere in the index if they attempt to look up this term.

The content of See identifies another term in the index which the reader should consult instead of the current term.

Processing expectations

Suppressed. This element provides data for processing but it is not rendered in the primary flow of text.

It is possible for multiple IndexTerms, taken together, to form an illogical index. For example, given the following IndexTerms:


<indexterm><primary>Extensible Markup Language</primary>
<see>XML</see></indexterm>
<indexterm><primary>Extensible Markup Language</primary>
<secondary>definition of</secondary>
</indexterm>

there's no way to construct a logical index because an entry in the index should never have both a see and other content.

DocBook cannot detect these errors. You will have to rely on an external process to find them.

Future Changes

The InterfaceDefinition element will be discarded in DocBook V4.0. It will no longer be available in the content model of this element.

Parents

These elements contain see: indexterm.

Examples

For examples, see indexterm.