Page 1 of 1

Problems using custom XLST-FO engines

Posted: Wed Apr 16, 2008 4:50 pm
by superturbo
Hi,
For some reason oxygen wants to rename my two input files called: a_xo_till_acf220se.xml and acf220se.xfo when using a custom engine which will transform these file to a pdf.

I you look at the error message you can see that the program renames the xml file to:
a_xo_till_acf220se.xml_xml

And that the .xfo file (xls) is being renamed to:
oxy28268.xsl

Is this a bug or did I miss something here?
Note that im using ${xml} for the input xml fil, ${xsl} for the input xsl file (acf220se.xfo) and ${out} for the output file which is not yet specified.

error message below:

SystemID: C:\xmltrans\acf220se.xfo
Description: xlmtransform not found. Make sure it is installed properly and the PATH env variable points to the parent dir of the executable.

SystemID: C:\xmltrans\acf220se.xfo
Description: Cannot run program "fop.bat -xsl C:\xmltrans\oxy28268.xsl -xml C:\xmltrans\a_xo_till_acf220se.xml_xml I:\Systems\PDF" (in directory "C:\xmltrans"): CreateProcess error=2, The system cannot find the file specified

Re: Problems using custom XLST-FO engines

Posted: Thu Apr 17, 2008 12:18 pm
by sorin_ristache
Hello,

The input files are not renamed or modified by the transformation. oXygen creates some temporary files from the input files for applying the transformation. a_xo_till_acf220se.xml_xml and oxy28268.xsl are temporary files.

It seems that the errors are caused by an incorrect command line set for the custom XSL-FO processor. The command line tries to start an executable called xlmtransform but the executable is specified with a relative path and it cannot be found when the relative path is appended to the working directory set for the custom processor.


Regards,
Sorin

Re: Problems using custom XLST-FO engines

Posted: Fri Apr 18, 2008 12:26 pm
by superturbo
Thanks for the reply, you were indeed right. This is how the .bat file I used to transform two files into an pdf looks like. I'm not sure how to run the rem command from oxygen, or exactly what that command does. I'd be thankful for anyhelp on this matter.

Code: Select all


rem pushd ..\..\..\Programvare\fop-0.20.5rc

cd\XMLTransForm_Batch\Programvare\fop-0.20.5rc

fop.bat -xsl c:\XMLTransForm_Batch\CreditCaseNewRelease\test.xfo -xml c:\XMLTransForm_Batch\CreditCaseNewRelease\test.xml -pdf c:\XMLTransForm_Batch\CreditCaseNewRelease\test.pdf
rem popd

Re: Problems using custom XLST-FO engines

Posted: Fri Apr 18, 2008 12:32 pm
by sorin_ristache
In a Windows batch file the rem command is just a comment that does nothing. I do not know what you try to do but if you want to run a pushd executable located in the same folder with the Windows batch file you have to use a command without the 'rem' word:

Code: Select all

pushd ..\..\..\Programvare\fop-0.20.5rc
Regards,
Sorin