RE: [xep-support] RE: trouble with keep with next

Victor,

Your description is very close to my issue. You did a much better job of
showing the problem.

I interpret within-column to mean precisely that, that your adjacent blocks
remain within the same column. To me that doesn't mean a column cannot span
multiple pages. Therefore, I would think a page break would be allowed (keep
in mind I am not the guy from RenderX, I'm just a user).

My problem comes down to the inability for me to prevent two adjacent blocks
from receiving a page break between the two. Ideally, what I believe I need
is:
<fo:block keep-with-next.within-page="always"> MY HEADER </fo:block>
<fo:block keep-with-previous.within-page="always"> Unknown Amount of Data
</fo:block>

What I sometimes end up with is "MY HEADER", which is always just one line,
being printed at the bottom of the page, then a page break, then "Unknown
Amount of Data" begins printing on the next page. I can't have "MY HEADER"
sitting alone at the bottom of the page or it looks kind of silly.

I've dealt with this issue before by nesting the two blocks within another
block like this:

<fo:block keep-together="always">
   <fo:block keep-with-next.within-page="always"> MY HEADER </fo:block>
   <fo:block keep-with-previous.within-page="always">Known Amount of Data
</fo:block>
</fo:block>

I was able to do that because I was certain the combined text "MY HEADER"
and "Known Amount of Data" was always going to be small enough to fit in a
page. In my current case "Unknown Amount of Data" could be any length.

Jerry J

-----Original Message-----
From: owner-xep-support@renderx.com [mailto:owner-xep-support@renderx.com]
On Behalf Of Victor Mote
Sent: Thursday, August 23, 2007 1:22 PM
To: xep-support@renderx.com
Subject: RE: [xep-support] RE: trouble with keep with next

Hi All:

Ken Holman wrote:

> >The documentation says that keep-with-next.within-page="always"
> >isn't supported.
>
> Yes, I read that as well ... perhaps your problem is insoluble given
> this restriction (which seems very explicit in the documentation).

Actually, the doc says (4.10 User Guide, p. 91) ".within-page component is
unsupported; it is mapped to .within-column." In my case, I have only one
column, with the following (abbreviated) FO:

<fo:block keep-with-next="always" keep-together="always" ... </fo:block>
<fo:block keep-with-previous="always" keep-with-next="always"
keep-together="always" ... </fo:block>
<fo:block keep-with-previous="always" keep-together="always" ... </fo:block>

XEP places a page-break between the second and third blocks. I have always
interpreted "keep-with-next.within-column" to be a superset of
"keep-with-next.within-page". In other words, it does not seem possible to
satisfy "within-column" without also satisfying "within-page". So is my
understanding of this wrong, or does the documentation really mean to say
"we don't break pages for keep-with-next, we only break columns"?

If what I have described is not the expected behavior for XEP, I'll be happy
to provide a concise document that shows the problem. I just want to be sure
of what I should expect before going to that trouble.

My apologies if this should be a separate thread. It seemed related ...
enough.

Victor Mote

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/terms-of-service.html

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html
Received on Thu Aug 23 16:10:14 2007