<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Preface: I am using XEP 4.19 (I have developer version with XEP
marks on each page, client has full version)<br>
<br>
I have been attempting to apply logic to a table that is rendered in
a two column layout. The logic would:<br>
<br>
1. keep the first and second rows in the same columns (always)<br>
2. keep the second-to-last and last rows together in the same column
(always).<br>
<br>
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.<br>
<br>
The table/table row code looks essentially like:<br>
<br>
<fo:table><br>
<fo:table-row
keep-with-next.within.column="always"><fo:block>.....</fo:block></fo:table-row><br>
<fo:table-row><fo:block>.....</fo:block></fo:table-row><br>
<fo:table-row><fo:block>.....</fo:block></fo:table-row><br>
....<br>
<fo:table-row><fo:block>.....</fo:block></fo:table-row><br>
<fo:table-row
keep-with-previous.within-column="always"><fo:block>.....</fo:block></fo:table-row><br>
</fo:table><br>
<br>
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).<br>
<br>
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.<br>
<br>
So, something like:<br>
<fo:block> //this is a section<br>
<fo:block>...some text.....</fo:block><br>
<fo:table><br>
<fo:table-row
keep-with-next.within.column="always"><fo:block>.....</fo:block></fo:table-row><br>
<fo:table-row><fo:block>.....</fo:block></fo:table-row><br>
<fo:table-row><fo:block>.....</fo:block></fo:table-row><br>
....<br>
<fo:table-row><fo:block>.....</fo:block></fo:table-row><br>
<fo:table-row
keep-with-previous.within-column="always"><fo:block>.....</fo:block></fo:table-row><br>
</fo:table><br>
<fo:block> ... rest of text for section ....
</fo:block><br>
</fo:block><br>
<rx:flow-section> //one column layout<br>
<fo:block>...</fo:block><br>
</rx:flow-section><br>
<br>
<br>
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.<br>
<br>
(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)<br>
<br>
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.<br>
<br>
Thank you in advance.<br>
<br>
:dr:<br>
<br>
<div class="moz-signature">-- <br>
<div style="color:#444;font-size:14px;font-weight:bolder;margin:0
0 5px 0;">Daniel Reed</div>
<div style="color:#444;font-size:12px;line-height:16px;">
Founder/Managing Director<br>
p: +1 617.684.0182 x201<br>
f: +1 814.284.0182<br>
<a class="moz-txt-link-abbreviated" href="mailto:dan.reed@wrycan.com">dan.reed@wrycan.com</a><br>
<a class="moz-txt-link-freetext" href="http://www.wrycan.com">http://www.wrycan.com</a><br>
</div>
<div style="font-size:10px;color:#999;border-top:1px #999
solid;border-bottom:1px #999 solid;margin:10px 0 0 0;padding:4px
0 4px 0;">
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.
</div>
</div>
!DSPAM:87,4f2732d263734243118310!
</body>
</html>