[xep-support] Re: possible issue with keep-with-next on table-row

Kevin Brown kevin at renderx.com
Mon Jan 30 17:54:42 PST 2012


Daniel:

 

We would need the actual FO to do any commenting. You can send to me
directly or post to support at renderx.com as you are a supported customer.
There is no sense in guessing without seeing the actual FO.

 

Kevin Brown

RenderX

 

 

 

From: xep-support-bounces at renderx.com
[mailto:xep-support-bounces at renderx.com] On Behalf Of Daniel S. Reed
Sent: Monday, January 30, 2012 5:41 PM
To: RenderX Community Support List
Subject: [xep-support] possible issue with keep-with-next on table-row

 

Preface: I am using XEP 4.19 (I have developer version with XEP marks on
each page, client has full version)

I have been attempting to apply logic to a table that is rendered in a two
column layout.  The logic would:

1. keep the first and second rows in the same columns (always)
2. keep the second-to-last and last rows together in the same column
(always).

The sample I have been working from is client content that has a two column
page master that has text in the first column, the start of a table at the
end of the first column, the remainder of the table in the second column,
and some text to fill out the rest of the second column.

The table/table row code looks essentially like:

<fo:table>
    <fo:table-row
keep-with-next.within.column="always"><fo:block>.....</fo:block></fo:table-r
ow>
    <fo:table-row><fo:block>.....</fo:block></fo:table-row>
    <fo:table-row><fo:block>.....</fo:block></fo:table-row>
    ....
    <fo:table-row><fo:block>.....</fo:block></fo:table-row>
    <fo:table-row
keep-with-previous.within-column="always"><fo:block>.....</fo:block></fo:tab
le-row>
</fo:table>

This works, as I believe it should.  I then tested this code against an
example in the actual BOOK which was used as the example of why the logic
above should be applied, and it did not work. The first row is orphaned in
the first column (in the example in the source content).

The difference I could find is that after the table and the rest of the para
text, there is a switch to ONE COLUMN layout using the rx:flow-section
element.

So, something like:
<fo:block> //this is a section
    <fo:block>...some text.....</fo:block>
    <fo:table>
        <fo:table-row
keep-with-next.within.column="always"><fo:block>.....</fo:block></fo:table-r
ow>
        <fo:table-row><fo:block>.....</fo:block></fo:table-row>
        <fo:table-row><fo:block>.....</fo:block></fo:table-row>
        ....
        <fo:table-row><fo:block>.....</fo:block></fo:table-row>
        <fo:table-row
keep-with-previous.within-column="always"><fo:block>.....</fo:block></fo:tab
le-row>
    </fo:table>
    <fo:block> ... rest of text for section .... </fo:block>
</fo:block>
<rx:flow-section> //one column layout
    <fo:block>...</fo:block>
</rx:flow-section>


If I remove the rx:flow-section from the FO by hand and rerun the example,
the logic for keep-with-next works as I expect.  I was able to add a
"<fo:block> </fo:block> between the section block and the rx:flow-section
and this has it working as expected... but I wondered if there was something
about the flow-section that is taking precedence over my keep-with-next.

(please note, I also tried using keep-with-previous on the 2nd row and
keep-with-next on the 2nd to last row just to be sure)

I can ask the client if I can release a snippit of their content/FO, but if
I do, I would like to do so directly to an XEP engineer.

Thank you in advance.

:dr:

-- 

Daniel Reed

Founder/Managing Director
p: +1 617.684.0182 x201
f: +1 814.284.0182
dan.reed at wrycan.com
http://www.wrycan.com

CONFIDENTIALITY: This message and any attachments are the property of
Wrycan, Inc. They may contain privileged and confidential information
intended only for the use of the addressee named above. You are hereby
notified that any use, dissemination, distribution or reproduction of this
message and attachments is prohibited. If you received them in error, please
notify the sender and delete them immediately. 

!DSPAM:87,4f2732d263734243118310! 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20120130/66ab9fcd/attachment.html>


More information about the Xep-support mailing list