Currently, the property net.sf.jasperreports.default.font.name in the jasperreports.properties file only applies when no font is specified in the JRXML report design. If a font is defined at the report level, the report-level font takes precedence over the global configuration.
In our case, we are trying to configure a CJK-compatible font (for example Arial Unicode MS CJK) at the global level to support multilingual characters. However, when exporting reports to PDF, the configured CJK font is not applied if a different font is defined inside the JRXML report.
This results in CJK characters not rendering correctly in the PDF export, while modifying each JRXML report individually is not feasible in environments where a large number of reports already exist.
A server-level or library-level configuration that can enforce a global font (even when fonts are defined at report level) would help ensure proper CJK character rendering in PDF outputs.
Please find the below case for more details,
https://support.tibco.com/wolken-support/allcases/request-details?requestId=2548995
Nagarajan M
| Components | Import/Export, JasperReports Library, JasperReports Server, JasperSoft Studio |
