On 09/30/2011 11:27 AM, Alberto Perri wrote: > I have been comparing Apache FOP (Vrsn: fop-1.0) with RenderX XEP (Vrsn: > xep-4.19-20110414) XSL-FO using processors using XMLmind XSL Utility > (Vrsn: 4.5.0-01) to render DITA Files into PDF format. In doing so, i > have observed that Apache FOP does not properly handle the > <xsl:attribute name="keep-with-next.within-page">always</xsl:attribute> > option according to the XMLmind XSL-FO Converter Conformance Statement.
The XMLmind XSL-FO Converter Conformance Statement is about XMLmind XSL-FO Converter, our in-house XSL-FO Processor. This Conformance Statement does *not* apply to: * FOP, which is the work of The Apache Software Foundation. See http://xmlgraphics.apache.org/fop/compliance.html * XEP, which is the work of RenderX. See http://www.renderx.com/reference.html#XslFoConformance > You will notice from the PDF snap shots below that the Apache FOP places > a break between "2.1.1 Bay: BFO and its accompanying image wheres > RenderX XEP does not. > Output from Apache FOP > Output from RenderX XEP > Other than the conversion specification for either Apache FOP or RenderX > XEP to convert DITA files to PDF all other options in the XMLmind XSL > Utility are the same. Yes, you have uncovered a limitation of FOP. > Is there a specific way i need to specify the <xsl:attribute > name="keep-with-next.within-page">always</xsl:attribute> option for > Appache FOP? The Appache FOP has shown unable to handle <xsl:attribute > name="keep-together.within-page">always</xsl:attribute> option either. > Please let me know if there is a specific way i need to specify the > "keep-with-next" and "keep-together" attribute options using Appache FOP. Thank you for this information. Sorry, but we don't know any workaround for the FOP limitation you have reported. You should ask your question to the FOP developers. -- XMLmind DITA Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/ditac-support
