Dear Mr. Shafie, 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) <font embed-url="fonts/dejavu-lgc/DejaVuLGCSans-Bold.ttf"> 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 ? <font embed-url="fop-config:fonts/dejavu-lgc/DejaVuLGCSans-Bold.ttf"> Thank you! Philippe. 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: nobili, philippe Sent: Friday, March 10, 2017 11:21 AM 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 Are you sure this happens with ALL DocBook 4 documents Dear Mr. Shafie, Yes, absolutely. Even with tiniest DocBook document created from scratch. The same for DobBook-5.1. All other output formats work as previously (XXE-6.3), the only exception is PDF using FOP. As we guessed yesterday, the problem is somewhere in our DocBook (4,5) customization layers (it works with the stock DocBook4). The odd thing is that the DocBook-4 customization hasn't changed these past months, and does not cause any trouble of this kind with XXE-6.3/FOP. Many thanks for your support, Best regards, Philippe. 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: xmleditor-support-boun...@xmlmind.com [mailto:xmleditor-support-boun...@xmlmind.com] On Behalf Of Hussein Shafie Sent: Friday, March 10, 2017 8:54 AM 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 nobili, philippe wrote: > Humm, it's odd. We just launched the deployment script, as usual. I'll double > check. Are you sure this happens with ALL DocBook 4 documents or on the contrary, with just one specific DocBook 4 document? nobili, philippe wrote: > We rebuilt XXE-7.3 on JNLP form scratch with no more luck... we did the same > with XXE-6.3 form scratch and it works fine... > > So something has changed; our guess is that it might come from our > customization layer ? In our customization layers, we have specialized XSLT > stylesheets for FO, they are declared "locally", so the <transform> goes like > this: > > <transform stylesheet="xsl/fo/default_custom.xsl" file="__doc.xml" > to="__doc.fo"> [...] <transform> When you convert your DocBook document to PDF, you should see the following messages (Category "Command Execution" in the "Message Log" dialog; see http://www.xmlmind.com/xmleditor/_distrib/doc/help/statusTool.html): --- Transforming XML file "__doc.xml" to "__doc.fo" using "xsl/fo/default_custom.xsl" Compiling stylesheet "jar:/.../default_custom.xsl" ... Converting XSL-FO file "__doc.fo" to "__doc.pdf" using FOP FOP XSL-FO processor error: java.lang.IllegalArgumentException: URI is not absolute --- Therefore the error, which is reported AFTER the execution of the XSLT engine, cannot be caused by your "xsl/fo/default_custom.xsl". > > The 'default_custom.xsl' loads in turn the stock file, that is > 'docbook-config:xsl/fo/profile-docbook.xsl'. Could it be an issue with FOP > on JNLP ? > > This works locally and also on JNLP with XXE-6.3, so we are in the mist. I would be glad to help if I could reproduce the bug here at XMLmind, but this is not the case. If you want to solve this issue as fast and as efficiently as possible, please consider zipping the folder containing ALL the files created by deployxxe (http://www.xmlmind.com/xmleditor/_distrib/doc/configure/deploy_webstart_procedure.html) and sending me privately a link allowing me to download this (large) archive. I'm afraid we'll both loose our time if you don't do this. -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support 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
