This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hello, I have a XML file, and a XSL-FO file created with XF Designer 2008, and a XSL file created with XF Designer 2008 too. I tried to transform the XSL-FO using apache fop 0.94 version to PDF or PCL, but I have errors. The xsl-fo document have graphs, and bar code, and so much text, some error is some like de border and padding must be 0, from de body configuration. Someone could help me?
I have found the FOP users mailing list to be very responsive on problems like this. They will also be interested in seeing a minimum example that demonstrates the problem.
Joined: Jul 04, 2008
Thank you for your help, I described a litle more my problem:
My XSL-FO file generated from my XML and the XSL generated with XF Designer 2008:
When I want process this XSL-FO file, with apache fop I have the following error: 07-07-08 12:17:59mainERROisf.domain.gcpr.XMLTransformHelperFOTrasform199transform(): org.apache.fop.fo.expr.PropertyException: Border and padding for region "xsl-region-body" must be '0' (See 6.4.13 in XSL 1.0).
To solve this problem, I put the the border and padding for region "xsl-region-body" in '0', but I have the following error: 07-07-08 12:45:10mainERROisf.domain.gcpr.XMLTransformHelperFOTrasform199transform(): org.apache.fop.fo.ValidationException: Error(Unknown location): For fo:simple-page-master, only one fo:region-start may be declared.
The lines that I�m running there are:
[ UD: removed the inline images to preserve the layout ] [ July 07, 2008: Message edited by: Ulf Dittmer ]
Joined: Jul 04, 2008
It could be that XSL file, generated with XF Designer 2008, is not apache fop compatible? Exist some other tools to process the XSL-FO file to generete PDF and PCL files?
Joined: Mar 22, 2005
This is too much code to go through and try to understand. What William and I were asking for is a minimal example of the problem. That means to remove as much code as possible, so that you can't remove anything from the rest and still have it exhibit the problem. In other words, an SSCCE.