A Java Reporting Component (JRC) XI Release 2 application exports a Crystal report to Portable Document Format (PDF). However, the exported PDF file displays a different font than the Crystal report does, or you may see question marks in place of certain fonts. This behavior does not occur when the report is exported to PDF using the Crystal Reports Designer.
Since the JRC is a 100% Java reporting solution, it can only use fonts that are accessible by the Java Runtime Environment (JRE). If the fonts are not accessible by the JRE, then the default font (typically san serif) is used.
Versions of the JRC previous to Crystal Reorts for Eclipse 2.0 do not embed or subset fonts into PDF files. This means that: (1) fonts must be available on the platform where the PDF file is viewed, or substitute fonts will be displayed; (2) the character encodings supported are either WinANSI (CodePage 1252) or an encoding used with the language packs supplied by Adobe (and not Unicode). If the font is not part of the WinANSI (CodePage 1252) font set, they are displayed as question marks in the PDF document.
For Crystal Reports Java (Crystal Reports for Eclipse 2.0) this is no longer an issue. For versions earlier than this, complete one of the following steps to display the original font:
" Install the fonts on the operating system where the JRC application is deployed. Refer to the operating system documentation for more information.
- OR -
" Install the fonts to the JRE that is running the JRC application by copying the font files to the JRE lib/fonts folder. Refer to the Fonts section of the Internationalization Guide in the Java SDK documentation for more information.
- OR -
Ensure that the fonts being used in the report are within the WinANSI 1252 CodePage.
JRE supports only TrueType and PostScript Type 1 fonts.
JAVA REPORTING COMPONENT JSP EXPORT ADOBE ACROBAT WRONG INCORRECT FONT CHANGED Crystal Reports Java Reporting Component Exporting Fonts , c2019128 , KBA , BI-DEV-JAV , BI Software Development Kits (SDKs) - Java , Problem