Re: Transforming Incompatible Stylesheets over to FOP Apache
Hi, FOP doesn't handle directly XSLT, but resulting XSL-FO. If an XSLT produces an XSL-FO that is not handled correctly by FOP, that be caused by, either... - not implemented feature (see FOP Compliance page [1]) (for example, in your XSLT *FIGURE*.xsl, I've found the fo:change-bar-begin but there can be other things) - old FOP version, - unresolved URI, - missing dependence, - etc. In order to get better and quicker help, you should provide some material: - FOP version - environment (OS, JVM, etc.) - how FOP is run (CLI, embedded, ...) - short XSL-FO (not XSLT) that points the issue - trace, or at least precise description of what you get Vs expect [1] http://xmlgraphics.apache.org/fop/compliance.html 2013/10/31 matrix ivan.teno...@lmco.com: Thanks for your post Rsargent. It makes sense that after looking at a few the Army stylesheets located in the link I provided you are pointing out they speak directly to S1000D. The MIL-SPEC-3031A is actually the Army's version of the S1000D standard. The Army borrows from the S1000D standard a lot of stylesheet related code. However, there are some differences on how the PDF looks like on paper. For example the 3031A standard requires the ICN number for a graphic appear on the lower right hand corner of a graphic. In contrast, the S1000D standard does not require the ICN number display on the page at all. Like this example, there are a bunch of other stylesheet related differences between the 3031A standard and S1000D standard that are too numerous to cover. Therefore, I somehow need to make the 3031A stylesheets I got from the Army work in harmony with my Arbortext Publisher app because currently it doesn't recognize them at all. It only recognizes the S1000D standard stylesheets that were included with Arbortext Publisher. From what I was told by the Arbortext technical support person the 3031A stylesheets are not compatible with Arbortext Publisher because they are not correctly coded to FOP Apache stylesheet coding conventions. My stylesheet coding skills are not strong enough to figure out how the 3031A stylesheet code deviates from FOP Apache stylesheet code. Therefore, I would be very grateful if anyone out there can take a good look at the XSL files inside the 3031A ZIP file and let me know how this code deviates from FOP Apache stylesheet coding conventions. In closing, the way I see it is I need to do one of two things: 1. Find a FOP Apache transformation engine that will transform my 3031A stylesheets to a format my Arbortext Publisher app likes. 2. I need to figure out how to modify the code to the existing S1000D FOP Apache stylesheets my Arborext Publisher app uses so that it follows all of the formatting rules the Army 3031A standard requires. Any info or suggestions that will help me make progress will be greatly appreciated. Thanks. -- View this message in context: http://apache-fop.1065347.n5.nabble.com/Transforming-Incompatible-Stylesheets-over-to-FOP-Apache-tp39504p39507.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Transforming Incompatible Stylesheets over to FOP Apache
I believe you are referring to the XSLT stylesheets used with the convenience function of FOP to support XML to XSL-FO transformation as a pre-processing step. Formally, this step is incidental to the functionality of FOP, whose only real task it transform XSL-FO documents into an output format. Since your concern is solely related to this pre-processing step, there isn't much documentation or other support with FOP for this task. Indeed, it is my opinion that this preprocessing step functionality should be removed from FOP entirely, forcing users to solely rely on external tools to create XSL-FO input for FOP. On Wed, Oct 30, 2013 at 2:48 PM, matrix ivan.teno...@lmco.com wrote: Fellow Forum Members, I'm using Arbortext Publisher which utilizes FOP Apache coded stylesheets to output a PDF compliant to the S1000D standard. However, I need to have my PDF publication conform to an Army military standard known as MIL-SPEC 3031A. These 3031A stylesheets are available for free download at the link below: https://www.logsa.army.mil/pub/s1000d/FO-3031-A00-USARMY-PARA_001-00_EN-US.zip My problem is a compatability related problem. The 3031A stylesheets the Army provides are not coded to the FOP Apache standard and therefore incompatible with Arbortext Publisher. In short, I'm not able to output my publication out of Arbortext Publisher as a 3031A compliant PDF. Since I'm new to FOP Apache, I'm hoping anybody out there can outline a strategy on what I need to do to convert the Army provided 3031A stylesheets over to FOP Apache stylesheets? Is there a transformation engine that accomplishes this task? Also, are there any online training videos that show how to modify FOP Apache stylesheet code? My thinking is maybe I could tweak the code so that my PDF outputs as something that looks close to a 3031A compliant publication. Any info will be greatly appreciated. . -- View this message in context: http://apache-fop.1065347.n5.nabble.com/Transforming-Incompatible-Stylesheets-over-to-FOP-Apache-tp39504.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Transforming Incompatible Stylesheets over to FOP Apache
As others pointed out, the default input for FOP is FO, not XSL and XML. Nevertheless you can use FOP to create an FO from XSL and XML: fop -xml my.xml -xsl my.xsl -foout input.fo Use that to generate a simple input.fo file and send it to this mailing list and then it will be easier to help. You can also try to bypass Arbortext and just use FOP: fop -fo input.fo -pdf output.pdf On 10/30/13, 9:48 PM, matrix wrote: Fellow Forum Members, I'm using Arbortext Publisher which utilizes FOP Apache coded stylesheets to output a PDF compliant to the S1000D standard. However, I need to have my PDF publication conform to an Army military standard known as MIL-SPEC 3031A. These 3031A stylesheets are available for free download at the link below: https://www.logsa.army.mil/pub/s1000d/FO-3031-A00-USARMY-PARA_001-00_EN-US.zip My problem is a compatability related problem. The 3031A stylesheets the Army provides are not coded to the FOP Apache standard and therefore incompatible with Arbortext Publisher. In short, I'm not able to output my publication out of Arbortext Publisher as a 3031A compliant PDF. Since I'm new to FOP Apache, I'm hoping anybody out there can outline a strategy on what I need to do to convert the Army provided 3031A stylesheets over to FOP Apache stylesheets? Is there a transformation engine that accomplishes this task? Also, are there any online training videos that show how to modify FOP Apache stylesheet code? My thinking is maybe I could tweak the code so that my PDF outputs as something that looks close to a 3031A compliant publication. Any info will be greatly appreciated. . -- View this message in context: http://apache-fop.1065347.n5.nabble.com/Transforming-Incompatible-Stylesheets-over-to-FOP-Apache-tp39504.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
