Preformatted Text

Used for preformatted text, such as computer code, in which white space (such as tabs, line feeds, and spaces) should be preserved

This element’s content typically is displayed or printed in a monofont to preserve character alignment.


The @position attribute may be used to indicate whether this element must be anchored at its exact location within the text or whether it may float, for example, to the top of the next page, next column, to the end of a logical file, or within a separate window. For the typical <preformat> element, the “float or anchor” decision will be governed by the size of the object. For example, short code fragments are typically anchored whereas full programs are typically placed elsewhere such as in a separate window or at the end of the article.


id Identifier
Orientation Orientation
position Position
preformat-type Type of Preformatted Text
specific-use Specific Use
xml:lang Language
xml:space Space

Related Elements

Poetry may be tagged with the <preformat> element if spacing is critical, but usually poetry should be tagged with the <verse-group> element, which may not preserve the exact indentation, but is likely to be displayed in a proportional font.

Content Model

<!ELEMENT  preformat    %preformat-model;                            >

Expanded Content Model

(#PCDATA | alt-text | long-desc | email | ext-link | uri | attrib | permissions | bold | italic | monospace | overline | roman | sc | strike | underline | abbrev | named-content | styled-content | sub | sup)*


Any combination of:

This element may be contained in:

<alternatives>, <app>, <bio>, <body>, <boxed-text>, <chem-struct>, <chem-struct-wrap>, <disp-formula>, <fig>, <license-p>, <named-content>, <p>, <sec>, <styled-content>, <table-wrap>, <td>, <th>


<p>Trees, of course, are hardly a random choice for our 
methodology.... Hierarchical trees have been understood as a 
way of viewing document structures since the earliest days of 
SGML development. Our initial tree structure was very simple:
&lt;!ELEMENT  implications  (tree+) &gt;
&lt;!ELEMENT  tree          (root, branches) &gt;
&lt;!ELEMENT  root          (term, synonym?) &gt;
&lt;!ELEMENT  branches      (term | (term, synonym) | tree)* &gt;
Terms are the literal strings for which the Ferret engine searches; they 
are the most specific expressions to be found in real documents of the 
concepts on which classifications rules act.</p>...