The RTF Rendering Extension of Telerik Reporting produces RTF v1.6 files. It is reccommended that the exported file is viewed with Microsoft Word 97 or later.
Telerik Reporting relies on Frames to a achieve a WYSIWYG layout and preserve the original report outlook as much as possible. Consumer applications that do not support Frames might produce unexpected results and are not recommended.
- Vertical Alignment is not supported.
- Report Background Color is not supported.
- TextWrap = false is not supported.
- Inset and Outset Borders are not supported.
- Rotated Text is rendered by an image.
- RTL Text Handling is left to the consumer application.
- Maximum Page Width and Height is 22 inches.
- Simple ReportItems (such as TextBoxes, PictureBoxes, etc.) cannot span on multiple pages. They should fit on a single page.
- Table of contents interactivity actions (navigational links) are not supported.
When a report contains a Table or a CrossTab item, the RTF Rendering Extension switches to an alternative rendering mode and uses tables since they are natural for those two items.
When a report is exported to RTF in the Table mode it is represented by a series of tables nested in one another representing the hierarchical structure of the report. Each container (for example a ReportSection or Panel) is rendered as a table and its child elements are positioned in the respective row and column of this table. The rows and columns of the table are calculated and sized depending on the locations and sizes of the child elements. Non-container items (for example a TextBox or PictureBox) are rendered as the contents of the cell they fall in. If a child element is a container itself, then a new table is nested in the respective cell.
Due to the media limitations, the following CSS style properties set on the HTML tags are NOT respected:
- background-color on Block elements is rendered as background-color of the text
- text-align (including the center tag)
- The report is paged by the consumer application (MS Word most often) based on the table generated and the page size. The exact number of pages might not be the same as in the Image Rendering Extensions.
- Since the paging is left to the consumer application the page breaks might not be at exactly the same spots as in the Image Rendering Extensions.
- The GroupSection.PrintOnEveryPage is not respected
- KeepTogether properties might produce slightly different results from the ImageRendering Extensions in certain circumstances, since the decision of whether a certain table row can be kept together on the current page is taken by the consumer application.
- Page widths that are up to 22 inches wide are supported.
- If the report grows more than the page width, the page will be automatically expanded to accommodate the report if possible.
- If an item’s bounds (location and size) are exactly or close to the page bounds (i.e. the item occupies exactly one page entirely), an additional page might be added after it.
Page Headers / Footers
- Page Headers/Footers are rendered by using the native page header/footer of the document and are always rendered on every page. PrintOnFirstPage/PrintOnLastPage properties are not respected.
- If the report is part of a ReportBook, then it does not render its Page Header/Footer.
- Contents inside the Page Header/Footer are rendered with tables as well.
- The global objects PageNumber and PageCount are inserted as calculated fields.
- BackgroundImages are usually not rendered. Only if the container has no children or the simple item has no content its BackgroundImage will appear. So, for example, if you have a Panel with TextBoxes inside it, then it will not render its BackgroundImage.
- Item borders are rendered as cell borders on the cell that the item occupies.
- Mixing a lot of items that are not aligned to each other in the same container increases the complexity of the generated table, thus increasing document rendering and opening times and file size.
- Text boxes grow when they contain non-breaking spaces.
- When text is exported, text with font decoration in certain fonts may generate unexpected or missing glyphs in the rendered report.
- Some older readers do not support nested tables and other crucial features so export results may be unexpected. The recommended application for opening RTF files generated by Telerik Reporting is Microsoft Office Word 2007.
- Watermarks are not supported.
- Table of Contents is not supported.
- BackgroundImage.Repeat in PageSettings is not respected, since the RTF natively supports tiled background patterns.
- If a TextBox item with justified text is rendered on two or more pages, the last line of each page (except the last page) will be left-aligned due to the justification algorithm used by RTF.
This rendering extension does not support any interactive features.