Mailing-List: contact fop-user-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: fop-user@xml.apache.org
Message-ID: <40557CBB.60106@hotmail.com>
Date: Mon, 15 Mar 2004 09:51:55 +0000
From: Chris Bowditch <bowditch_chris@hotmail.com>
Reply-To: bowditch_chris@hotmail.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20031013 Thunderbird/0.3
MIME-Version: 1.0
To: fop-user@xml.apache.org
Subject: Re: Print on demand using FOP
References: <4051D482.2020503@acu.ac.uk>
In-Reply-To: <4051D482.2020503@acu.ac.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Mike Brodbelt wrote:

<snip/>

> How do other people deal with this? Is there any way to exercise control
> over the positioning of pacge breaks without needing widow/orphan
> support? Any work rounds possible. Failing that (stupid question alert),
> any idea when a version of FOP that supports this might make an appearance?

The trouble with the current version of FOP 0.20.5 is that the code is 
written in such a way that it makes adding support for keep-* properties 
too difficult. This is the main reason for the redesign effort. FOP has 
been re-written with keep-* properties in mind. However, progress on the 
redesign is slow. Its such a big job and the FOP team is low on 
resource. Help is always welcome though ....

In terms of how I deal with this issue today. I'm ashamed to say this on 
list, but we use RenderX's XEP when keep-* properties are required.

Chris


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org