[
https://issues.apache.org/jira/browse/FOP-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18011291#comment-18011291
]
Joao Goncalves commented on FOP-3056:
-------------------------------------
I only got FOP to fail if the font is requested in the FO. If the font is not
in the FO, it will never be loaded so nothing verifies it's validity.
The only thing the config will check is that the font has an embed-url, not the
contents of the file.
> Fop Font "strict-configuration" option set to false dont work as expected
> -------------------------------------------------------------------------
>
> Key: FOP-3056
> URL: https://issues.apache.org/jira/browse/FOP-3056
> Project: FOP
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Erik Billerby
> Priority: Major
>
> While trying to get around FOP-3054, I am noticing that setting the
> strict-configuration config property to false does not work as expected:
> {quote}Setting this option to 'true' will cause FOP to strictly verify the
> contents of the FOP configuration file to ensure that defined resources (such
> as fonts and base URLs/directories) are valid and available to FOP. Any
> errors found will cause FOP to immediately raise an exception.
> {quote}
> Even with the property set to false FOP halts execution with an IOException
> when a font definition like the following is not found on the file system:
> {quote}
> {{<font kerning="yes" embed-url="/usr/share/fonts/opentype/Pebble-CAPS.otf">}}
> {{<font-triplet name="Pebble" style="normal" weight="400"/>}}
> {{</font>}}{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
