If the fonts used are the ones in the PDF specification that are commonly known as standard type 1 fonts or the base fourteen fonts, then fonts are not embedded for ANSI content. If one or more of these conditions is not met, the font is not embedded in the PDF file.Īlthough the conditions are met, there is one circumstance under which fonts are not embedded in the PDF file. If all of these conditions are met for a font, the font is embedded in the PDF file. Fonts are embedded only when they are needed to display the rendered report data. If a font is referenced by an item that has the Hidden property set to True, the font is not needed to display rendered data and will not be included in the file. For more information, see "TTGetEmbeddingType" on .įonts are referenced by visible items in a report. If the property value is EMBED_NOEMBEDDING, the font is not embedded in the PDF file. Installed fonts include a property that indicates whether the font author intends to allow embedding a font in a document. If the referenced font is not installed on the report server, the resulting PDF file might not contain the correct mappings and might not display correctly when viewed.įonts are embedded in the PDF file when the following conditions apply:įont embedding privileges are granted by the font author. When the report server generates a report in PDF format, it uses the information stored in the font referenced by the report to create character mappings within the PDF file. Fonts that are used in the report must be installed on the report server. When possible, the PDF rendering extension embeds the subset of each font that is needed to display the report in the PDF file. You can create and modify paginated report definition (.rdl) files in Microsoft Report Builder, Power BI Report Builder, and in Report Designer in SQL Server Data Tools. This topic provides PDF renderer-specific information and describes exceptions to the rules. The PDF renderer is a physical page renderer and, therefore, has pagination behavior that differs from other renderers such as HTML and Excel.
See PDF Rendering Extension conformance to ISO 14289-1, Power BI Report Server & SSRS for details. The PDF rendering extension also conforms to ISO 14289-1 (PDF/UA) standards for Accessible PDF.
For more information about the limitations, see Export Reports (Report Builder and SSRS). The PDF rendering extension supports ANSI characters and can translate Unicode characters from Japanese, Korean, Traditional Chinese, Simplified Chinese, Cyrillic, Hebrew, and Arabic with certain limitations. However, PDF viewers such as Adobe Acrobat are required to view or print a report in PDF format.
The rendering extension does not require Adobe software to render the report. Although PDF 1.3 is compatible with Adobe Acrobat 4.0 and later versions, Reporting Services supports Adobe Acrobat 11.0 or later. The PDF rendering extension renders paginated reports to files that can be opened in Adobe Acrobat and other third-party PDF viewers that support PDF 1.3. APPLIES TO: ✔️ Microsoft Report Builder (SSRS) ✔️ Power BI Report Builder ✔️ Report Designer in SQL Server Data Tools