Secondary output transformations

Typefaces and Fonts

The font characteristics: reverse and frame are not supported.

If a typeface selection scheme is referenced in a mapping the converter will use it to determine the typeface to use. For HTML-based secondary transforms, all of the typeface names are used in the CSS style. For RTF transforms, only one typeface is used.


The supplied output plugins for the secondary output transformations do not attempt any significant processing of images. In general, images are included as is, so properties such as rotation will not be honored. The image may not appear at all if it is in a format that the output medium does not support. For example, TIFF graphics generally won’t appear in HTML output because most browsers don’t support this format.

The architecture of the transformation mechanism allows additional or modified plugins to be created to modify images as required. See the Transform Manual in the Programmer Documentation for more information.


Nested tables are only partially supported in secondary output transformations.

Some of the advanced features of CALS tables, such as multiple tgroup elements and entrytbl elements, cannot be represented in HTML or RTF tables.

Some table formatting such as rules and background shading are not supported in all output formats, or may differ in appearance from the paged output.

Headers and Footers

Headers and Footers are not written to secondary outputs.


Sidenotes are not written to secondary outputs.


When images are included in the text of a footnote, the RTF produced by the secondary output transformation causes some versions of Microsoft Word to crash. The RTF can be successfully read by WordPad and OpenOffice.


Fills (dot fill, space fill and rule fill) are not supported in HTML-based outputs.

RTF supports fills subject to some restrictions. Only one type of fill is supported in a paragraph (for example, a paragraph cannot contain both space and rule fills). RTF output will contain at most one fill object per line, unlike TopLeaf paginated output which may contain several fills in a line.

Text Direction

Right-to-left text is not supported.


Secondary outputs can only be generated from XML documents