Used for preformatted text, such as computer code, in which whitespace (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.
Conversion Note: 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.
<!ELEMENT preformat %preformat-model; >
Any combination of:
<abstract> Abstract; <ack> Acknowledgments; <app> Appendix; <app-group> Appendix Group; <body> Body of the Article; <boxed-text> Boxed Text; <chem-struct> Chemical Structure (Display); <chem-struct-wrapper> Chemical Structure Wrapper; <disp-formula> Formula, Display; <disp-quote> Quote, Displayed; <fig> Figure; <gloss-group> Glossary Group; <glossary> Glossary Elements List; <named-content> Named Special (Subject) Content; <notes> Notes; <p> Paragraph; <> Reference List (Bibliographic Reference List); <sec> Section; <supplementary-material> Supplementary Material; <table-wrap> Table Wrapper; <td> Table Data Cell (XHTML table model); <term> Definition List: Term; <th> Table Header Cell (XHTML table model); <trans-abstract> Translated Abstract
<article> <front> ... </front> <body> ... <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: <preformat> <!ELEMENT implications (tree+) > <!ELEMENT tree (root, branches) > <!ELEMENT root (term, synonym?) > <!ELEMENT branches (term | (term, synonym) | tree)* > </preformat> 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>... </body> <back> ... </back> </article>
... <p>As you can see in the following excerpt, use of literal result elements is very convenient: <preformat> <xsl:template match="div/divhead" priority="2"> <<named-content content-type="literal result">h2</named-content>> <xsl:apply-templates/> <<named-content content-type="literal result">/h2</named-content>> </xsl:template> </preformat></p> ...