Ken Holman Wrote:
Have you tried putting in your one template rule the following test:
<xsl:if test="not(parent::foo)">
<xsl:attribute name="keep-together">always</xsl:attribute>
</xsl:if>
Not yet, but I was thinking of something along these lines. I probably
over-complicated my first question by introducing the idea of nested
results. Initially my aim was to get the top level fo:blocks not
breaking first, and then move on to a solution for the child elements.
regards
Andy
________________________________________________________________________
This e-mail and its attachments are confidential. If you are not the intended
recipient of this e-mail message, please telephone or e-mail us immediately,
delete this message from your system and do not read, copy, distribute,
disclose or otherwise use this e-mail message and any attachments.
Although ri3k Limited believes this e-mail and any attachments to be free of
any virus or other defect which may affect your computer, it is the
responsibility of the recipient to ensure that it is virus free and ri3k
Limited does not accept any responsibility for any loss or damage in any way
from its use.
ri3k Limited
Registered in England: 10-12 Ely Place, London, EC1N 6RY
Company Number: 3909745
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list