Export to RTF
- 4 minutes to read
This document describes specifics of exporting a document to the RTF format (Rich Text Format).
A code example illustrating how to export a report to RTF is available at How to export a report to RTF format.
The RtfExportOptions.ExportMode property specifies how a document is exported to RTF.
- In the RtfExportMode.SingleFilePageByPage mode, the export follows the WYSIWYG paradigm: the report’s page headers and footers, and top and bottom margins appear on every page of the resulting document as they appear in the report’s Print Preview. Elements residing in your report are treated as frames in the resulting file.
- In the RtfExportMode.SingleFile (continuous) mode, a multi-page report is converted into a single document with a table-like layout: the report’s page headers and footers are repeated only once - at the beginning and end of the resulting document.
Not all programs that can be used to view and edit RTF files can correctly process the resulting RTF file. For instance, Microsoft® Word® displays these files correctly, while WordPad® does not. Note that this is not due to any problem in our product - WordPad does not fully support the RTF standard.
The following table lists RTF-specific options and indicates which export modes support these options:
Specifies whether to include the existing text and image watermarks in a RTF file.
Specifies the range of pages which should be exported to RTF.
Specifies whether the height of table rows in a resulting document should have fixed values.
Defines whether the header and footer contents should be displayed on the first page of the final document.
Specifies whether page breaks should be included in the resulting RTF file.
Take into account the following specifics, when exporting a document in the RtfExportMode.SingleFile mode:
As a workaround, use subreports to combine multiple reports into a single document. Alternatively, export all your reports to RTF files separately and then join all the exported data into a single file.
Only report controls that do not intersect with each other can be correctly exported to RTF. Otherwise, the resulting file may have a broken layout.
To preserve your report’s layout in the RTF format, enable the report’s DesignerOptions.ShowExportWarnings property at design time, and ensure that there are no exclamation marks shown for intersecting controls (colored in red).
When exporting a document to RTF in a table-like layout, the actual height of table rows in the resulting file can be adjusted by the Microsoft® Word® rendering mechanism automatically to fit the content. This can lead to increasing the page layout and produce a result that differs from the initial document in Print Preview. To avoid this and make the row height unaffected by adding new content, set the FormattedTextExportOptions.KeepRowHeight property to true.
Leaving this property set to false (its default value) results in the height of table cells having non-fixed values. Adding a new line of text to a cell’s content increases the row height.
KeepRowHeight = false KeepRowHeight = true
- To locate controls’ content in native header and footer sections of the resulting RTF file, place these controls in the TopMarginBand or BottomMarginBand (not in the page footer and header).
Vector images (e.g., pictures, charts or bar codes) are always rasterized on export to RTF. You can use the PageByPageExportOptionsBase.RasterizationResolution property to define the image resolution.