Mark Gaywood - 13/Feb/10 11:11 AM I've check-in a version, sadly for who-knows-why I can't test it on my machine (too many servers I suspect). It appeared that an <fo:block> was being closed before containing a <fo:table> within an <fo:table-cell>. Subsequently, no Wordings section. I leave this open until it's fully tested. Also, looks like the xsl:fo spec is being altered to be in-line with XHTML that means the "font-family" and few other attributes need to be rethought as they'll need to be expressed in a "style" attribute. This should only effect us when we upgrade FOP and saxon/xalan

Dick Anderson - 09/Mar/10 07:50 AM - edited Might not be at all relevant, but I just spotted this. Could it be the root of the problem?? In the XSL, the template for itemData looks like this:     <xsl:template match="itemData">         <!-- resolve classes-->         <xsl:if test="text()!=''">            [SNIP]         </xsl:if>     </xsl:template"> And the XML source looks like this:   <chapterData id="c3" title="Terms and Conditions" class="string">     <block title="Terms and Conditions" class="string" placement="body" applicability="all">       <itemData title="Terms and Conditions" class="wording">         <p class="term-title">           <b>Policy Cancellation</b>           <br />         </p>         [SNIP]       </itemData>     </block>   </chapterData> The xsl:if test="text()!=''" in the XSL looks like it would always prevent the wordings from being populated - because the wordings are just text floating inside an itemData element.

Mark Gaywood - 09/Mar/10 12:55 PM Actually, you may have inadvertently found it. This <xsl:if test="text()!=''">, basically say do while not empty. But, this is only when there is no text. All the information for the T&C information are within other elements, so we should be checking for children too. OK I should be checking something in this evening. Thanks Dick