Hi,
It isn't necessary to customize the template with match="entry" to add the keep-together properties, as there is a utility template named "table.cell.properties" that can accomplish that. This is a template, not an attribute-set, and is described in this section of my book:

http://www.sagehill.net/docbookxsl/PrintTableStyles.html#table.cell.properties

Just add this to the customized template:

<xsl:attribute name="keep-together.within-column">always</xsl:attribute>

Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]


----- Original Message ----- From: "Vincent Hennebert" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, November 07, 2008 3:28 AM
Subject: Re: [docbook-apps] table vertical spans and page breaks


Hi,

Marcel Tromp wrote:
Hi,

I am using fop 0.95. I am using code similar to this example:

I've tried using this dbfo at different location as well (row, start of table) and I don't see any difference: fop breaks the table in the middle of a cell that straddles multiple rows.

      <tbody>
        <row>
          <entry>
            <para>foo</para>
          </entry>
          <entry>
            <para>foo</para>
          </entry>
          <entry morerows="19">
            <?dbfo keep-together="always"?>
            <para></para>
          </entry>

This processing instruction only applies to formal object (table,
example, figure, equation), not to other elements [1].
[1] http://docbook.sourceforge.net/release/xsl/current/doc/pi/dbfo_keep-together.html

You will have to customize the template matching <entry> and add
a keep-together.within-column="always" to the produced fo:table-cell
element. As to how to do that...


What I am trying to do is to have a long (500 row) narrow, sorted table be printed three columns per page. I want to use the straddled cell to control page breaks:

page 1:
1 6 11
2 7 12
3 8 13
4 9 14
5 10 15

page 2:
16 21 26
17 22 27
18 23 28
19 24 29
20 25 30

page 3:
etc.

I’m not sure this is the best way to achieve that. The source DocBook
file should remain output-agnostic; by adding a row-spanning entry
element you’re somehow abusing its semantics.
A more proper way would be to customize the XSLT stylesheets so as to
put a keep-together.within-column plus keep-with-next.within-column on
every row, except every n-th row. Of course that requires some XSLT
knowledge.


HTH,
Vincent

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to