J. Knisley wrote:
> Thanks, I actually found the command line utilities after I emailed you.
> They work very well. Do you think these are production worthy?
Yes.
> I just need a command line tool I can use to transform one single document at
> a time to a word document...nothing fancy, no threading or anything like that
> is needed.
This is the case.
>
> Could you elaborate on this comment, "We have found mandatory to pass a
> fo-processor parameter( with "XEP", "FOP" and "XFC" as its value) to our XSLT
> stylesheets because *all* XSL-FO processors have their limitations."
>
Excerpts from one of our XSLT stylesheets:
---
<xsl:template name="twoColumns">
<xsl:param name="width1">1</xsl:param>
<xsl:param name="width2">1</xsl:param>
<xsl:choose>
<xsl:when test="$foProcessor = 'FOP'">
<!-- FOP does not support table-layout=auto. -->
<xsl:attribute name="table-layout">fixed</xsl:attribute>
<xsl:attribute name="width">100%</xsl:attribute>
<fo:table-column column-number="1"
column-width="proportional-column-width({$width1})"/>
<fo:table-column column-number="2"
column-width="proportional-column-width({$width2})"/>
</xsl:when>
<xsl:otherwise>
<xsl:attribute name="table-layout">auto</xsl:attribute>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
---
The app invoking this XSLT stylesheet passes it XSLT parameter
foProcessor = FOP or XEP or XFC to ensure to get the best output given
the target XSL-FO processor.
--
XMLmind FO Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xfc-support
