DocBook to PDF on v8.2 (w/ attachment)
Hi I'm trying DocBook transformation to PDF for the first time. I followed the configuration parameters as per the Help pages (btw, some menus in Help pages are not up-to-date with 8.2). I tried all Saxon and Xalan transformers. I consistently get a Java error message, on one very long line, in the attached file. Would much appreciate any guidance of getting it to work (I didn't have this problem with v.8.1). Regards, Khaled Aly
Hello, That error is reported only with an older version of the predefined Docbook PDF scenario, that is one automatically imported from a previous version of oXygen. The one that comes with oXygen 8.2 changed the values of some XSLT stylesheet parameters necessary for the new version of Apache FOP included in oXygen 8.2. The old values of the parameters do not work with the new version of Apache FOP. If you have also previous versions of oXygen installed you should see the predefined scenario "Docbook PDF v8.2" in the list of transformation scenarios. Please use this scenario. Other option is to execute the action Options -> Restore Default Transformation Scenarios to remove the predefined scenarios of older versions and after that use the scenario "Docbook PDF". Regards, Sorin Khaled Aly wrote:
Would much appreciate any guidance of getting it to work (I didn't have this problem with v.8.1).
Hello Sorin Thanks for your response. I did restore default scenario and transformation was successful. I actually was required to de-install v8.1 for the 8.2 installation to succeed. I ensured there are no traces of old version in Program files and registry. What kind of toolset is meant by the "transformation scenario" and where could they have been residing? There are also several transformer options, what difference the choice should make? Finally, and not greedily :), what is the shortest path to customizing the XSLT-FO in order to control the output PDF format? Appreciate your help. Regards. Khaled ----- Original Message ----- From: "Sorin Ristache" <sorin@oxygenxml.com> To: <oxygen-user@oxygenxml.com> Sent: Friday, July 20, 2007 6:11 PM Subject: Re: [oXygen-user] DocBook to PDF on v8.2 (w/ attachment)
Hello,
That error is reported only with an older version of the predefined Docbook PDF scenario, that is one automatically imported from a previous version of oXygen. The one that comes with oXygen 8.2 changed the values of some XSLT stylesheet parameters necessary for the new version of Apache FOP included in oXygen 8.2. The old values of the parameters do not work with the new version of Apache FOP. If you have also previous versions of oXygen installed you should see the predefined scenario "Docbook PDF v8.2" in the list of transformation scenarios. Please use this scenario. Other option is to execute the action Options -> Restore Default Transformation Scenarios to remove the predefined scenarios of older versions and after that use the scenario "Docbook PDF".
Regards, Sorin
Khaled Aly wrote:
Would much appreciate any guidance of getting it to work (I didn't have this problem with v.8.1).
oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hello, The transformation scenarios from older versions are stored in the user preference folder, that is [user-home-folder]\Application Data\com.oxygenxml. You don't have to remove this folder when you upgrade to a new version. If you remove it you have to enter again the license key and you start with the default preferences. For customizing the PDF output you have to edit the XSLT stylesheet that generates the XSL-FO code. You can find the stylesheet in the scenario. For the scenario Docbook PDF the stylesheet is: ${frameworks}/docbook/xsl/fo/docbook.xsl ${frameworks} is the folder "frameworks" of the oXygen install folder. Regards, Sorin Khaled Aly wrote:
Hello Sorin
Thanks for your response. I did restore default scenario and transformation was successful.
I actually was required to de-install v8.1 for the 8.2 installation to succeed. I ensured there are no traces of old version in Program files and registry. What kind of toolset is meant by the "transformation scenario" and where could they have been residing?
There are also several transformer options, what difference the choice should make?
Finally, and not greedily :), what is the shortest path to customizing the XSLT-FO in order to control the output PDF format?
participants (2)
-
Khaled Aly -
Sorin Ristache