On 03/10/2017 11:56 AM, nobili, philippe wrote:
We finally figured out what seems to cause the problem with XXE-7.3/FOP, that
we do not see with XXE-6.3.
That was quite a struggle to find it... It is related, not to our DocBook
layers per-se, but to the fact that they use a customized FOP addon, the
purpose being to embed the required greek fonts by default.
So, we do something like this:
<property name="XXE_FOP_CONFIG" url="true">fop-config:fop.conf</property>
'fop-config:' is the prefix defined in the FOP addon. In the 'fop.conf' file,
we point to the embedded FONT files, e.g.: (excerpt)
This is OK.
<font embed-url="fonts/dejavu-lgc/DejaVuLGCSans-Bold.ttf">
This is OK.
Our FOP addon hasn't changed in years, so it seems that this was working
previously (for JNLP deployment), and does not work anymore. Does it seem
right, and if yes, would this fix the issue ?
But FOP itself has.
As explained in a previous email, currently we use Apache FOP 2.1; see
http://www.xmlmind.com/xmleditor/addons_doc.html#fop1_foprocessor
The stock FOP add-on compatible with XXE v6.3 included FOP 1.1.
May be now FOP 2.1 cannot resolve
"fonts/dejavu-lgc/DejaVuLGCSans-Bold.ttf" against a "jar:/" base URL.
(This happens only when XXE is deployed using Java Wen Start.)
<font embed-url="fop-config:fonts/dejavu-lgc/DejaVuLGCSans-Bold.ttf">
File "fop.conf" is loaded by FOP itself. I don't see how FOP could
translate "fop-config:" to something meaningful using XXE's XML catalogs.
I don't know which version of FOP you use in your custom FOP add-on,
therefore it's difficult to me to help you. For that, I must reproduce
the issue here at XMLmind. The simplest is to allow me to download your
custom FOP add-on.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
