Oxygen XML Forum

Our publishing pipeline was developed by a previous employee 5+ years ago, and it has worked well for all team members on Windows machines since then. One of my team members is now using a Mac, and the associated PDF output is missing some content. This is the first instance of a team member using a Mac with this pipeline.

Our pipeline was designed around Oxygen Editor 22, Chemistry, and a company-specific plug-in that extends com.oxygenxml.pdf.css. Our plug-in uses several XSLT stylesheets to add attributes to some elements prior to generating the merged file. The console output indicates that our company-specific plug-in is being invoked, but the merged file is missing the attributes. It appears that the pipeline, when run from the Mac system, is either not recognizing the XSLT stylesheets or not honoring the rules in them. However, the process works as intended on Windows systems.

I suspected a configuration issue, but I’ve compared every configuration setting in Options > Preferences between our Windows and Mac systems, and I can’t find any meaningful differences that might cause this.

Any suggestions?

I think you need to debug this stepwise. Difficult to guess what is wrong. I guess this is a file separator issue somewhere in your customizations.

Hello,

Besides what Stefan said you can try to add some <xsl:message> elements in your plug-in XSLT stylesheets to see if the templates are correctly called, the parameters correctly passed and the attributes correctly set.

Regards,
Julien

Besides what Stefan said you can try to add some <xsl:message> elements in your plug-in XSLT stylesheets to see if the templates are correctly called, the parameters correctly passed and the attributes correctly set.

Thanks! I'll give that a try and see if I can pinpoint exactly where the process is failing.

Thank you, Julien!

Adding some <xsl:message> elements helped me verify that our XSLT stylesheets were functioning correctly. After that, I discovered the Mac system wasn't interpreting our build file the same way as our Windows systems. I added a different attribute to one of the ANT instructions, and it fixed the problem.

I appreciate your help!