Seems to be related to: https://issues.apache.org/jira/browse/FOP-2600
Indeed, adding: <font-base>./<font-base> (not sure what was the rationale not having './' be the default BTW....) does not work either. Philippe. [cggsigbanner] Philippe Nobili Subsurface Imaging - Product Engineering Tel: +33 16447 4090 | Mobile: +33 63756 6441 CGG, 27 avenue Carnot Massy, 91341 - France http://www.cgg.com<http://www.cgg.com/> Please consider the environment before printing. From: nobili, philippe Sent: Friday, March 10, 2017 12:58 PM To: 'xmleditor-support@xmlmind.com' Subject: RE: [XXE] Cannot convert DocBook to PDF using FOP when XXE v7.3 is deployed using Java Web Start May be now FOP 2.1 cannot resolve "fonts/dejavu-lgc/DejaVuLGCSans-Bold.ttf" against a "jar:/" base URL. This is exactly the conclusion we came to. I don't know which version of FOP you use in your custom FOP add-on We 100% rely on XXE's FOP, we do not deliver FOP itself. The only purpose of Our FOP customization is to embed the required *.ttf files. I guess that any "fop.conf" (top: <fop>) defining relative font paths should allow you to reproduce the problem on JNLP; I attach ours if it can help (the *.ttf files themselves come from DejaVu-LGC). Many thanks again, Philippe. Our setup : In our DocBook configuration: <property name="XXE_FOP_CONFIG"> url="true">fop-config:fop.conf</property> In our FOP configuration: * we declared the 'fop-config:' prefix (rewritePrefix) * we placed the fop.conf file and the listed *.ttf files Philippe Nobili Subsurface Imaging - Product Engineering Tel: +33 16447 4090 | Mobile: +33 63756 6441 CGG, 27 avenue Carnot Massy, 91341 - France http://www.cgg.com Please consider the environment before printing. -----Original Message----- From: Hussein Shafie [mailto:huss...@xmlmind.com] Sent: Friday, March 10, 2017 12:41 PM To: nobili, philippe Cc: 'xmleditor-support@xmlmind.com' Subject: Re: [XXE] Cannot convert DocBook to PDF using FOP when XXE v7.3 is deployed using Java Web Start 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. This email and any accompanying attachments are confidential. If you received this email by mistake, please delete it from your system. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited.
-- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
