title

Processing expectations

Formatted as a displayed block. Titles are often repeated in several locations, for example, at the location where the object occurs, in the table of contents, and in running headers and footers.

DocBook does not offer any mechanism for indicating where a line break should occur in long titles. Titles are often repeated and no single line break is likely to be correct in all of the places where a title is used. Instead, you will have to rely on your processing system to provide a mechanism, such as a processing instruction, for identifing the location of forced line breaks.

There are some contexts in which a Title can appear more than once. For example, it may appear in both Book and BookInfo:

<book><title>Some Book Title</title>
<bookinfo>
  <title>Some Book Title</title>
  <author><firstname>Some</firstname><surname>Author</surname>
    </author>
</bookinfo>
…

In these contexts, if the Title occurs more than once, the same title must be used in both places. It is an error to use different titles, although DocBook has no way to detect the error.

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 title: abstract, appendix, appendixinfo, article, articleinfo, authorblurb, bibliodiv, biblioentry, bibliography, bibliographyinfo, bibliomixed, bibliomset, biblioset, blockinfo, blockquote, book, bookinfo, calloutlist, caution, chapter, chapterinfo, colophon, constraintdef, dedication, equation, example, figure, formalpara, glossary, glossaryinfo, glossdiv, glosslist, important, index, indexdiv, indexinfo, itemizedlist, legalnotice, lot, msg, msgexplan, msgmain, msgrel, msgset, msgsub, note, objectinfo, orderedlist, part, partinfo, partintro, personblurb, preface, prefaceinfo, procedure, productionset, qandadiv, qandaset, refentryinfo, reference, referenceinfo, refsect1, refsect1info, refsect2, refsect2info, refsect3, refsect3info, refsection, refsectioninfo, refsynopsisdiv, refsynopsisdivinfo, sect1, sect1info, sect2, sect2info, sect3, sect3info, sect4, sect4info, sect5, sect5info, section, sectioninfo, segmentedlist, set, setindex, setindexinfo, setinfo, sidebar, sidebarinfo, simplesect, step, table, task, taskprerequisites, taskrelated, tasksummary, tip, toc, variablelist, warning.

Children

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