The PDF Rendering Extension of Telerik Reporting produces a version 1.6 PDF file. The file can be
opened with Adobe Acrobat 7.0 or later. The file is compressed using the FlateDecode filter.
The PDF rendering extension is a physical page renderer, thus has pagination behavior that differs
from other rendering extensions such as HTML and Excel, which are not page oriented. PDF and Image Export Formats share the same high-level layout engine. Therefore all rules and design considerations that apply for the
Image Rendering Extension apply for PDF as well.
The PDF rendering extension is based on the Image rendering extension, with some differences. For
information common to the Image rendering extension and the PDF rendering extension, see
Design Considerations for Image Rendering.
This topic describes features that are specific to the PDF rendering extension.
Font Requirements
The PDF rendering extension embeds fonts by default. This functionality is controlled by the
FontEmbedding device informattion setting. Fonts that are used in a report
must be installed on the machine where the application is running, so the PDF rendering can embed them. If you disable font embedding,
the fonts used in the report must be installed
on the client computers used to view the report. When the report engine generates a report in PDF format, it uses the information
stored in the font to measure and create character mappings within the PDF file. If the referenced font is
not installed on the machine where the application is running, the resulting PDF file might not contain the correct mappings and might
not display correctly when viewed. Before deploying the report on a production server, you should test the PDF output on client computers
to verify that the report renders correctly. Do not rely on the Designer Preview or rendering to HTML, because GDI font
substitution in those formats behaves differently than PDF. If there are Unicode Glyphs missing on the server, you may see characters
replaced with a question mark and if there is a font missing on the client, you may see characters replaced with boxes.
 Caution |
|---|
When designing a report that would be exported to PDF, you should make sure that the font you use in the report supports
the characters that would be displayed. For example when you use a font that does not support non-Latin characters, but then
non-Latin characters are added to the report and it is exported to PDF, they would be replaced by question mark character (?)
as PDF doesn’t automatically substitute fonts.
|
To view the list of fonts that are embedded in a PDF file, open the file in Adobe Acrobat and from the File menu, view
Properties. The Fonts tab displays the list of fonts that are embedded in the file.
Metadata
The PDF rendering extension writes the following information to the PDF file:
| PDF property | Value |
|---|
| Creator | Telerik Reporting product name and version. |
| Producer | Telerik Reporting product name and version. |
| CreationDate | Report execution time. |
Limitations
The PDF Rendering extension has the following limitations:
- Only Unicode fonts are supported.
- PDF Security features such as password and encryption are not supported.
Interactivity
Bookmarks
The PDF rendering extension supports Document Map
interactive feature which is rendered as PDF Bookmarks. You can use the Bookmarks by opening the Bookmarks pane in Acrobat
Reader to navigate inside the report.
Hyperlinks
URL actions on report items are rendered as hyperlinks in the PDF file. Hyperlinks are rendered as clickable
links and when you click the hyperlink, the default Web browser opens and navigates to the specified URL.
See Also