Re: [xep-support] Problem with keep-together properties

From: Michael Sulyaev <>
Date: Tue Apr 26 2005 - 05:13:12 PDT

Hello, Neha.

If I got you right, you expect the following behavior of the formatter:
1. try to render the whole block on the current page
2. if not enough space, start it on the next page
3. if it does not fit on the next page, go back and start it on the
first page and break where appropriate.

XEP will try to render a block on one page if there is a
keep-together.within-page="always" property on the block.
What you want is "if not fits one page - go back, remove keep
constraint and re-render the block". This algorithm cannot be achieved with XEP,
and is not required from an implementation by the XSL-FO spec.

Nevertheless, you may try to create a iterative system, that would
analyze XEP intermediate format (XEPOUT) (by using rx:pinpoints), make
changes into the input FO according to your rules, and call XEP again
to format the changed input. This will be quite complicated and

Best regards,
 Michael Sulyaev                
Monday, April 25, 2005 at 9:54:29 PM you wrote:
NP> Hi All,
NP> I have a problem with  keeping the blocks of text together in
NP> one page. Our requirement is like this.
NP> "If the text block exceed one page, and there is space to
NP> start it on one page and complete it on the next page, start
NP> the text on the first page and continue on the next page,
NP> otherwise start the text on a next page (When text can fit in next
NP> page and not in the previous page)."
NP> Each block contain some data which need to be grouped
NP> together. I tried keep-together.within-page property, but this
NP> property is not giving me the desired results.
NP> Thanks,
NP> Neha
NP> __________________________________________________
NP> Do You Yahoo!?
NP> Tired of spam?  Yahoo! Mail has the best spam protection around 
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
Received on Tue Apr 26 06:02:43 2005

This archive was generated by hypermail 2.1.8 : Tue Apr 26 2005 - 06:02:44 PDT