RTF Output

Area in UI	Limitation
Text category	• The Shading property is not supported for inline elements. • Because of limitations in MS Word, the curvy underline styles will be mapped to the jagged style in RTF output • The Words Only setting for strikethrough is not supported • Strikethrough color settings are not supported - strikethrough will be displayed in the current font color. • The Offset measure option for super- and subscript fonts is not supported. This is a limitation of MS Word.
Spacing category	• Line spacing variations are not supported - spacing will always be set to single line • Precedence settings for Spacing before and Spacing after are ignored - space will be accumulated and the largest amount allocated
Breaks category	• Widow and orphan control via the Print/PDF Keeps button and associated Keeps dialog box are not supported • Priority settings for keeps are ignored. • Keeps can only be applied within the on same page scope • In the Start new field, a setting of Column is treated as Page. • When electing start a new page, no blank pages will occur when it appears one should be forced. For example, if the current page is page 1 and an element starts a new odd page, a new page numbered 3 starts, showing odd header/footers. No page 2 will be emitted. • Setting a number of columns for a new page is not supported when the page is created via the Start new: Page option Changing the number of columns can only be done at Page Set level, which corresponds to a section in MS Word. • The Landscape page body for duration of element option is not supported
Generated text category	Settings made on the Generated text category are ignored if you are working with RTF styles. • Settings made in the Insert Leaders, Rule or Space dialog box are not used - see the Insert > Leaders, Rule and Space menu option in the Generated Text Editor • Change bars are not supported - see the Insert > Begin Change Bar and Insert > End Change Bar options in the Generated Text Editor • It is recommended that you set up indexing using Word styles - settings made in the Generated text category (see the Insert > Index option ) are not supported See Creating a Index with Nesting Element Model Index Terms for further limitations when creating an index for RTF output. • The Start At option for numbering (see the numbering dialog boxes accessed via the Edit button next to the Bullets and Numbers field) is only supported if you are not using Word styles. Exporting to RTF using Word styles can only generated hard coded numbers, not those calculated dynamically. • The Custom counter option for numbering (see the numbering dialog boxes accessed via the Edit button next to the Bullets and Numbers field) is only supported if you are not using Word styles. Exporting to RTF using Word styles can only generated hard coded numbers, not those calculated dynamically. • Page numbers and footnote numbers in RTF only support the “cjk-earthly-branch” or “cjk-heavenly-stem” numbering styles. Any of the other non-Latin styles in these contexts will be displayed in the decimal style in RTF output. Note that alphabetic and roman numeral page and footnote numbers are permitted • Settings made in the Repeat title or continuation text field are ignored • Graphics inserted via generated text (see the Insert > Graphic menu option in the Generated Text Editor) must be presented in a format acceptable for web viewing when they are referenced. The processing process will not carry out a conversion to web-friendly format. • The Specified Horizontal Space option in the Format > Print/PDF menu in the Generated Text Editor is not supported. Any value will appear as a single space. • Generated text configured for a property set will be resolved to the contexts/conditions that reference the property set when the stylesheet is exported.
Side by side category	• Side by side layout is not supported in RTF output.
Page Sets list	Columns category • The Balance columns option is not supported. This is a limitation of Microsoft Word. Page numbers category • Division numbers inserted into a page set via the Insert > Division Reference option in the Generated Text Editor are only partially supported. A division number will be inserted by selecting this option but it cannot be updated/restarted dynamically as the divisions change within a single page set.
Page Regions list	Page regions will not be included in RTF output unless they can be identified as headers or footers. They need to match certain criteria: Header region: • Same left and right margins as the page body • Does not overlap the page body • Top aligned Footer region: • Same left and right margins as the page body • Does not overlap the page body • Bottom aligned
Generated Contents list	In general, extra work is required when setting up generated content objects to ensure that they can be updated dynamically in RTF output. Use Word field codes and refer to Word documentation for full details on how this can be achieved. • The Insert > Final Page Number option in the Generated Text Editor is not supported. • Division numbers inserted via the Insert > Division Reference option in the Generated Text Editor are only partially supported. A division number will be inserted by selecting this option but it cannot be updated/restarted dynamically as the divisions change within a single page set. • When electing to insert the content of an element via the Insert > Element Content menu option in the Generated Text Editor, the position options in the Insert Element Content dialog box are only partially supported: ◦ Specific occurrence within document: supported ◦ First started on page: not supported since RTF cannot process position information that is expected to be updated dynamically ◦ Last started on page: not supported, as above
Indexes list	• index-sort-as is not supported in RTF output. This is a limitation of MS Word. • index-see-also is only supported for the index term. You must manually enter the text See Also, or equivalent, as content of the index term to ensure it is output correctly. This is a limitation of MS Word.
Combined fonts list	• Combined fonts are not supported in RTF output.
Footnotes	• Footnote numbers in RTF only support the “cjk-earthly-branch” or “cjk-heavenly-stem” numbering styles. Any of the other non-Latin styles in these contexts will be displayed in the decimal style in RTF output. • Separator rule settings in the .style file (as well as spacing above the footnote) are ignored. The footnote separator rule is emitted by Word. • If you have set footnote numbering to restart at a division, this will only work properly if: The division starts a new page set and There are no elements that also start a page set within the element on which footnote numbering is set to restart This is a limitation of Microsoft Word.
Graphics	• Scaling settings for a graphic will only have an effect if the graphic is embedded. See the RTF tab of the Stylesheet Properties dialog box. • The Shrink graphics to fit option is not supported. • Default dpi differences between Windows and Unix mean that embedded graphics may appear cropped in RTF output generated via a Solaris or Linux PE server. To get results equivalent to that produced in a Windows environment, set defaultscreendpi=96 on the Unix machine.
Tables	• Nested tables are not supported in RTF output. This is a limitation of Microsoft Word. If a nested table appears in a document, it will be omitted when the document is published to RTF output.
General	• Word 97, and Excel 97, and earlier versions, are not supported • Index formatting specified in the Arbortext Styler UI (see the Tools > Format Index menu option) will not be reflected in indexes in RTF output. Refer to Microsoft Word’s online help for the ways in which index formatting can be defined.