Please test this patched FOP add-on and tell me if it works also OK for you.
Dear Mr. Shafie, Yes, it does ! We have tested the JNLP version of XXE with our DocBook addons on Windows and Linux and the PDF output is back again with the patched FOP you have provided. Many thanks for your help, 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: Hussein Shafie [mailto:huss...@xmlmind.com] Sent: Friday, March 10, 2017 6:55 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 It seems that FOP public APIs related to the resolution of URLs/URIs have completely changed between v2 and v1. These new URI-based APIs are now much more flexible, but are no longer able to resolve a relative URI against a "jar:" base. Older, simpler, APIs were URL-based and "jar:" URLs were not a problem. I had to *extend* FOP 2.1 (using its new APIs) to teach it how resolve to a relative URI against a "jar:" base. This patch will be available in XXE v7.4. --> Meanwhile, you may want to download a patched FOP add-on from this location: --- http://www.xmlmind.com/xmleditor/_download/fop1_foprocessor-7_3_0-PATCHED.zip --- March 10, 2017. 11408284 bytes. Note that I've tested it only with XXE v7.4 but I don't see why it would not be compatible with v7.3 too. Please test this patched FOP add-on and tell me if it works also OK for you. nobili, philippe wrote: > /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). > nobili, philippe wrote > 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. 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
