1 # Comments are treated as CDATA and not touched. It's best to set
2 # them out from other text if possible. A doublespace is nice but
3 # code is still code, so it's not really that important. (Down, inner
32 firstname surname othername
37 revnumber date authorinitials
52 section chapter glossary appendix
57 # "Normalize" means make smart whitespace decisions
58 para simpara example important note warning caution itemizedlist variablelist varlistentry entry quote figure glossdiv glossentry
72 emphasis literal abbrev
78 # Do not fubar <screen> or <programlisting>
82 # <entry> is special because a linebreak has meaning, best leave the
83 # decisions up to the experts
87 command application filename option userinput computeroutput replaceable glossterm
90 # The <primary> and <secondary> subelements of <indexterm> are still block
112 menuchoice guilabel guimenu guisubmenu guimenuitem guibutton keycap keycombo mousebutton
115 wordasword systemitem citetitle footnote email
121 # Make <ulink> and <xref> less goofy in their use of whitespace
126 creator description format identifier language maintainer omf relation subject type
132 # Cover rpm-info files
133 details rights version