Re: page-break-inside
OK thanks. It works now. Marcin Zawadzki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page-break-inside
Marcin Zawadzki wrote: Maybe I something dont understand. I have folowing problem with table rows: How to force table rows to be on one page only. When row is to big to fit on actual page it should be moved to next page. I try keeps nad breaks, but it seens to work in diffrent matter. That's exactly job for keep-together property [1], but make sure your row is able to fit on at least the entire page, otherwise you can run into infinite loop bug. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page-break-inside
> Marcin Zawadzki wrote: > > If somebody is working on property "page-break-inside" ? > No. Its way down the priority list because its basically redundant. > The only sensoble setting is page-break-inside="avoid", which is the > same as keep-together="always", simply replace it. Keep in mind > that keep-together only workss on table rows, so you might want > to use the old blind table trick. > > J.Pietschmann Maybe I something dont understand. I have folowing problem with table rows: How to force table rows to be on one page only. When row is to big to fit on actual page it should be moved to next page. I try keeps nad breaks, but it seens to work in diffrent matter. Marcin Zawadzki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page-break-inside
Marcin Zawadzki wrote: If somebody is working on property "page-break-inside" ? No. Its way down the priority list because its basically redundant. The only sensoble setting is page-break-inside="avoid", which is the same as keep-together="always", simply replace it. Keep in mind that keep-together only workss on table rows, so you might want to use the old blind table trick. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: page break
On Tue, 2002-07-23 at 09:08, RamanaJV wrote: > Then, > Is it possible to know, without actually rendering, how many lines a > block is expected to span. I really need this now in my application to get > away from the pagination problem that are occuring. Also, is it possible to > know, how many lines of text can be written on to a page with specific > dimensions? Only the layout process can determine how many lines a block will span. You can calculate how many lines will fit on a page by working out the line height or setting the line height (note the if the line height is set it uses a slightly different number, its a bug) and the spacing between blocks. You are probably better of rendering to xml then reading that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: page break
Then, Is it possible to know, without actually rendering, how many lines a block is expected to span. I really need this now in my application to get away from the pagination problem that are occuring. Also, is it possible to know, how many lines of text can be written on to a page with specific dimensions? Ramana. -Original Message- From: Keiron Liddle [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 12:37 PM To: FOP Subject: Re: page break On Tue, 2002-07-23 at 08:47, RamanaJV wrote: > > Devs, > Is it possible to tell FOP to clip the text, when the block will not > fit in the respctive region? I don't want the block to span across lines.. Currently no. This is something that will be implemented in the new design. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page break
On Tue, 2002-07-23 at 08:47, RamanaJV wrote: > > Devs, > Is it possible to tell FOP to clip the text, when the block will not > fit in the respctive region? I don't want the block to span across lines.. Currently no. This is something that will be implemented in the new design. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page-break-inside="avoid"
J Thanks for the reply. I was able solve my problem with the info you provided. Todd>>> [EMAIL PROTECTED] 07/17/02 06:10PM >>>Todd Migliore wrote:> My document contains one repeating block of data. The data varies in > length with each iteration. I need to force a page break if an > iteration of the block of data can not entirely fit on the current > page page. From what I understand page-break-inside="avoid" is the way > to go about this, unfortunately it seems this feature is not yet > implemented(version-0.20.3). Does anyone know of solution to this > problem? Thanks in advance.> > T Look here for hints: http://marc.theaimsgroup.com/?l=fop-user&m=102102545323696&w=2J.Pietschmann-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, email: [EMAIL PROTECTED]
Re: page-break-inside="avoid"
Todd Migliore wrote: > My document contains one repeating block of data. The data varies in > length with each iteration. I need to force a page break if an > iteration of the block of data can not entirely fit on the current > page page. From what I understand page-break-inside="avoid" is the way > to go about this, unfortunately it seems this feature is not yet > implemented(version-0.20.3). Does anyone know of solution to this > problem? Thanks in advance. > > T Look here for hints: http://marc.theaimsgroup.com/?l=fop-user&m=102102545323696&w=2 J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page break - broken
At 04:24 PM 7/25/01 +0200, Keiron Liddle wrote: > >I have found a problem with page breaks. ie. break-before and break-after. > >Due to changes in block where it now uses the property manager it no longer >handles the page breaks properly. > >It works if the block is directly under the flow but not for nested blocks. >The code in the property manager only operates if the parent area is a >ColunmArea. > >The attached diff should handle it better. > >I'm not sure about the implications though. Why is there special stuff for >Column and does that have any impact on nested blocks. Hi, Keiron If it's genuinely a page-break, then it doesn't matter what the parent is, you're right. If it's a column-context break, then we need code that looks like what is (was?) in there, although in order to handle nested blocks it should not assume that the area passed in is a ColumnArea; instead it should search out the ColumnArea ancestor. We need the ColumnArea in order to figure out what column it is, for starters. We'll get this right sooner or later. I'm hoping something like Peter West's Tree class will be the nucleus of a class that can quickly help us handle nested situations. Right now stuff is a hardcoded mess. As if that's news. :-) Regards, Arved Fairly Senior Software Type e-plicity (http://www.e-plicity.com) Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Page break problem in FOP 0.19.0
Hi Qi, Please attach your fo file (or at least part of it showing the problem if it's big) to your mail so that one of us can test it. Also, when you say it was OK with the CVS on 6/5, do you mean June 5 or May 6 (US or European date conventions? :-). That might help us figure out what changed in the 0.19.0 jar. Bye for now, Karen Lease > Qi Chen wrote: > > I have nested tables in my FO files and used to have premature page > breaks with FOP 0.18.1. After downloading the source code through CVS > and building fop.jar, the pages are properly generated. I downloaded > the source through CVS on 6/5/2001. > > But after downloading the FOP 0.19.0, the page doesn't break at all > and it goes all the way to the foot notes, throwing away the > left-over. Could anyone help me, please? thanks > > -Qi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
