Build.xml errors in latest update cause build to fail

locke955
Posts: 3
Joined: Wed Nov 08, 2017 7:58 pm

Build.xml errors in latest update cause build to fail

Post by locke955 » Wed Jan 17, 2018 7:58 pm

Hello,

I was using Chemistry with Oxygen XML and had no problems generating PDF documents from DITA maps. After updating Oxygen XML Editor to version 19.1, build 2017121318, PDF transforms fail every time. I made no modifications to my transformation scenario or referenced CSS file, but the build continues to fail with the following error message:

Code: Select all


Transformation failed. /Applications/Oxygen XML Editor/frameworks/dita/DITA-OT2.x/plugins/com.oxygenxml.pdf.css/build.xml:373: exec returned: 1
That line in the build.xml file is as follows:

Code: Select all

<exec executable="${css.processor.path.chemistry}" failonerror="true" logError="true">
The error code returns a 1, so it finds Chemistry, but will not build the PDF document. Did something change in the latest build of Oxygen XML Editor? Any help is greatly appreciated.

Cheers,

Adam

adrian
Posts: 2551
Joined: Tue May 17, 2005 4:01 pm

Re: Build.xml errors in latest update cause build to fail

Post by adrian » Fri Jan 19, 2018 5:10 pm

Hi,

In case anyone else encounters this, the problem is not triggered by an Oxygen update, but by a macOS update.
macOS 10.13 introduced a new font for emoji, "Apple Color Emoji.ttc" (~136MB ). This is huge by font standards.
The font detection that is used by both Apache FOP 2.2 and Oxygen PDF Chemistry 19.1 chokes on this particular font when trying to create the FOP fonts cache, <user_home>/.fop/fop-fonts.cache.

This issue affects all PDF transformations that use either Apache FOP or Oxygen PDF Chemistry.
A known workaround is to increase the memory for the FOP process to a very large value so that the detection passes at least once and creates the fonts cache.
e.g. For DITA transformations, edit the scenario, go to Advanced, JVM Arguments and specify -Xmx5000m (or -Xmx8000m).
e.g. For DocBook transformations (FOP only), go to Preferences, XML > XSLT-FO-XQuery > FO Processors, Memory available to the built-in FOP and specify 5000 (or 8000).
After running the PDF scenario successfully at least once (and the fonts cache was created), the memory can be reduced back to the default (or what value you have successfully used before).

We are currently working on a patch to avoid this problem.

Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

adrian
Posts: 2551
Joined: Tue May 17, 2005 4:01 pm

Re: Build.xml errors in latest update cause build to fail

Post by adrian » Thu Feb 15, 2018 1:57 pm

Hi,

I just wanted to let you know that this issue has been addressed in the latest maintenance build of Oxygen 19.1, 2018013010 (released on February 7th):
macOS 10.13/Apache FOP/Oxygen Chemistry: All PDF transformations using Apache FOP or Oxygen Chemistry were failing on macOS 10.13/High Sierra with an OutOfMemoryError.
This maintenance build is only available for the affected platform, macOS/OS X.

You can download it from our web site:
http://www.oxygenxml.com/download.html

The list of bug-fixes can be found here:
http://www.oxygenxml.com/build_history.html#2018013010

You can follow the release/build RSS feed here:
http://www.oxygenxml.com/rssBuildID.xml

Regards,
Adrian
Adrian Buza
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

Post Reply