[
https://issues.apache.org/jira/browse/FOP-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012191#comment-18012191
]
Joao Goncalves edited comment on FOP-3087 at 8/5/25 6:36 PM:
-------------------------------------------------------------
-I've seen the suggested fix and it makes sense why should do it, but I still
haven't been able to replicate the issue. I added my fo and xconf. I'm sure I'm
missing something.-
I cans see the example above doesn't even go through the transcoder. I've never
used it before, so I'll figure out how to use it and I'll apply the fix soon
after.
was (Author: JIRAUSER302961):
I've seen the suggested fix and it makes sense why should do it, but I still
haven't been able to replicate the issue. I added my fo and xconf. I'm sure I'm
missing something.
> PDFTranscoder fails to auto-detect system fonts by default
> ----------------------------------------------------------
>
> Key: FOP-3087
> URL: https://issues.apache.org/jira/browse/FOP-3087
> Project: FOP
> Issue Type: Bug
> Affects Versions: 2.5, 2.4, 2.6, 2.7
> Reporter: Julian Müller
> Assignee: Joao Goncalves
> Priority: Minor
> Attachments: fop.xconf, test.fo
>
>
> Contrary to the documentation, the PDFTranscoder fails to auto-detect system
> fonts by default, and also does not honor transcoding hint KEY_AUTO_FONTS =
> true.
> This is because the implicitly built configuration is not set up correctly.
> Line 163
> {code:java}
> c.addChild(fonts); {code}
> in AbstractFOPTranscoder needs to be moved after line 165, which is
> {code:java}
> fonts.addChild(autodetect); {code}
>
> A simple workaround to this problem is to explicitly pass a correctly set up
> configuration to PDFTranscoder, however, it would be preferable if
> PDFTranscoder would just honor its contract.
> I think this bug was introduced by FOP-2733, due to a subtle difference in
> Avalon's configuration package and its replacement. Avalon's configuration
> package allowed the addition of children in any order, but the new FOP
> configuration package adds copies instead of the original children, so the
> configuration tree needs to be built from the leaves to the root node.
> Currently, the code in AbstractFOPTranscoder does not follow this new
> requirement and instead builds the configuration tree from the root to the
> leaf.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
