The Noto Sans CJK fonts are CID-keyed CFF-flavored OpenType fonts (.otf). They were developed by Adobe Systems (the authors of PDF), so they fully conform to the OpenType and PDF specifications.
> When users save reports in PDF format, JasperReports Server generates the PDF output using Apache FOP (Formatting Objects Processor). In order for FOP to render fonts properly, you must install the font itself (for example, a TTF file) on the server host, create a font metrics file (using Apache’s org.apache.fop.fonts.apps.TTFReader utility), and update the userConfig.xml file to associate the font with its metrics. For more information, refer to the Apache FOP documentation.
The Apache FOP documentation regarding fonts is:
There, OTF are mentioned. That doc says
> OpenType Advanced Font Features
> OpenType fonts support advanced layout features such as ligatures, small caps, swashes, alternates, old style figures and more. Please see Advanced Typographic Extensions - OpenType Layout. These features are currently missing within FOP due to the implementation opting to favor a greater number of formats.
> While FOP may support embedding OpenType with advanced features in the future, the current method extracts the Compact Font Format (CFF) data containing among other things the character definitions, optionally subsets and embeds the result as a Type1C font. This allows the font to be used by both Postscript and older PDF versions while losing the features mentioned above. This is because embedding Open-Type in it's original state is only supported by PDF 1.6 and above.
Generally speaking, the Noto Sans CJK fonts need to be embedded in the PDF as CID-keyed Type1C.
My guess is that either Jasper or Apache FOP (which may be used by Jasper) have some problems dealing with the Noto Sans CJK fonts. I think you'd be best advised to contact the developers of Jasper to try resolve this issue.
Regards,
Adam Twardoch