Sure I opened this one - https://issues.apache.org/jira/browse/FOP-2600
On 22 March 2016 at 04:14, Pascal Sancho wrote:
> Hi,
>
> Please, can you file in a JIRA ticket to keep this in in mind.
>
>
> 2016-03-21 17:09 GMT+01:00 Adam Retter :
>>
Hi,
Please, can you file in a JIRA ticket to keep this in in mind.
2016-03-21 17:09 GMT+01:00 Adam Retter :
> Thanks for getting back to me Chris,
>
> Okay that makes sense to me then, and I was able to work with custom
> resolvers to get around the issue I have.
>
>
Thanks for getting back to me Chris,
Okay that makes sense to me then, and I was able to work with custom
resolvers to get around the issue I have.
However, you still have references in both your code and documentation
to , so it is not obvious that this has been removed!
Perhaps a little
Hi Adam,
I believe FOP Base was intentionally removed when FOP IO was reworked in
the v2.0 release. Which version are you upgrading from?
I seem to recall the developers couldn't think of a use case where Font
Base would need to differ from wildly from Base, and so Font Base was
It seems that fonts are not being resolved relative to the font-base
config parameter in 2.1, instead they are being resolved directly by
the ResourceResolver. This looks like a bug to me, can anyone confirm?
I have a FOP configuration file like this:
true
false
./