[oXygen-user] XSL-FO Docbook Transformation failing

Mark Wilson
Tue Aug 26 12:00:08 CDT 2008


Hello,
My Version is: 9.3, build 2008070211.

I had not seen the FOP tab at the bottom of the page. So I ran my own 
transformation again, and tab told me that the file fopConfiguration.xml had 
mixed content in a tag. The fopConfiguration file was created when I tried 
to add a font following the instructions in your document 
"addFontToFOP.pdf". I deleted fopConfiguration file and removed it from the 
fo processors configuration.

Then, to test FOP, I once again followed  the instructions for the Docbook 
transformation. This time it ran (which means FOP is OK in my copy of 
Oxygen). However, because my xml is not in Docbook form, it simply (and 
rightly) refused to produce an output with the message:

[Saxon-B] Note: namesp. add : added namespace before processing
[Saxon-B] ERROR: Document root element for FO output must be one of the 
following elements: appendix article bibliography book chapter colophon 
dedication glossary index part preface qandaset refentry reference sect1 
section set setindex.

Now that I know FOP is "working" (and could not produce a Docbook from a 
non-dockbook xml file), I would like to know what is wrong with my own 
transformation scenario. So, I ran my  own transformation scenerio again. A 
pdf file was created, but trying to open it failed with the message: 
"Acrobat could not open the file ... because it is either an unsupported 
file type or was damaged."

However, when I run FOP from the command line:
c:\Users\HP\fop-0.95-bin\fop-0.95\fop -xml krusty.xml -xsl krusty.xsl -pdf 
work\krusty.pdf produces a valid pdf document


How can I find out what in my transformation scenario is causing it to 
produce a corrupt pdf file?
Thanks,
Mark

--------------------------------------------------
From: "Sorin Ristache" <>
Sent: Tuesday, August 26, 2008 7:09 AM
To: <>
Subject: Re: [oXygen-user] XSL-FO Docbook Transformation failing

> Hello,
>
> The predefined transformations should generate the output without such 
> errors. You can see the FOP command line and the FOP output in a text 
> console at the bottom of the Oxygen window if you activate it with the 
> option "Enable the output of the built-in FOP" available in Preferences -> 
> XML -> XSLT/FO/XQuery -> FO Processors. Please post here the FOP output.
>
> What is your Oxygen version?
>
>
> Regards,
> Sorin
>
>
> Mark Wilson wrote:
>> In an attempt to render PDF via FO, I am reading the Oxygen Users Manual 
>> (pages 314-333) and am trying the Docbook PDF transformation described on 
>> pages 326-327. However, this transformation fails with an Error Msg 1 
>> which appears to be a FOP command line usage error. Since I cannot see 
>> the actual call to FOP from Ozygen, I have no idea how to fix this.
>>  I should also add that my FO and XSLT files run when I invoke FOP from 
>> the command line.
>>  Mark
> _______________________________________________
> oXygen-user mailing list
> 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
> 



More information about the oXygen-user mailing list