[
https://issues.apache.org/jira/browse/MPDF-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533317#comment-17533317
]
Michael Osipov commented on MPDF-104:
-------------------------------------
I have found your problem: doxia-module-fo comes with fo-styles.xslt which
sets the fonts. Those fonts are only the base fonts which represent Latin
scripts. Barely usable for most cases. The file can be overloaded, but I have
no idea whether the layers above expose the config for it. Apache FOP itself
basically use any font:
[https://xmlgraphics.apache.org/fop/2.7/fonts.html|https://xmlgraphics.apache.org/fop/2.7/fonts.html#awt]
I don't recommend use any system fonts because this would make the entire build
non-portable. Ideally, custom fonts are used which are open source and include
most of the Unicode space. Then on needs to decide whether a screen-optimized
or print-optimized font and which for serif and sans serif. I expect that the
estimated time for this is several days for someone who understands PDF, fonts
and Apache FOP. I do understand the two former pretty well, but not FOP. Maybe
the community can take care, I wil gladly consult.
[~slachiewicz], would you be interested in this?
> i18n broken
> -----------
>
> Key: MPDF-104
> URL: https://issues.apache.org/jira/browse/MPDF-104
> Project: Maven PDF Plugin
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Xavi Lee
> Priority: Major
> Attachments: 164194106-b4c23811-dee7-4849-abc4-6d88d7005d93.png,
> image-2022-05-07-20-26-03-180.png
>
>
> In mybatis release pdf, we can see it doesn't display the words of non
> English. It's "#".
> If you think it's not plugin problem, please give me a proper example for
> using i18n. !164194106-b4c23811-dee7-4849-abc4-6d88d7005d93.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
