Re: Keeping tables together with FOP 0.92b
The XSL-FO style approach would be not to use always for the keep property but an integer number. But this hasn't been implemented, yet. On 13.09.2006 21:15:13 cknell wrote: I' recently back to working with FOP. I have a document that consists of a number of tables with widely-varying numbers of rows. Sometimes several tables will fit entirely onto a single page, with others will span several pages. The problem I'm having involves those cases where a table almost fits onto a page, but one or two rows flow over onto the next page. I'd like to start a new page if the table won't fit onto the current one. I've tried some keep-with-previous tacks, but when a very long table won't fit onto a single page FOP errors out. Does anyone have a sure-fire method for causing a table to start on a new page if all the rows won't fit on the current page? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Keeping tables together with FOP 0.92b
Hi I'm not an experienced user, but have you tried keep-with-next? It did work for me, although with other undesired side-effects (see my post with the superlong title keep-with-next causes last row of previous table to come along. regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Keeping tables together with FOP 0.92b
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 9:15 PM I' recently back to working with FOP. I have a document that consists of a number of tables with widely-varying numbers of rows. Sometimes several tables will fit entirely onto a single page, with others will span several pages. The problem I'm having involves those cases where a table almost fits onto a page, but one or two rows flow over onto the next page. I'd like to start a new page if the table won't fit onto the current one. I've tried some keep-with-previous tacks, but when a very long table won't fit onto a single page FOP errors out. Hi, keep-with-previous property doesn't work for table list (see [1]) And this is not yet done in FOP_TRUNK (see [2]) Does anyone have a sure-fire method for causing a table to start on a new page if all the rows won't fit on the current page? If you know rows height, you can add an explicit page break when needed, for example using the XPATH sequence position() mod XXX, where XXX is the number of rows per page. Thanks. Charles Knell [1] http://xmlgraphics.apache.org/fop/knownissues.html [2] http://xmlgraphics.apache.org/fop/changes.html HTH, Pascal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Keeping tables together with FOP 0.92b
Pascal Sancho [EMAIL PROTECTED] wrote on 09/14/2006 07:47:09 AM: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 9:15 PM I' recently back to working with FOP. I have a document that consists of a number of tables with widely-varying numbers of rows. Sometimes several tables will fit entirely onto a single page, with others will span several pages. The problem I'm having involves those cases where a table almost fits onto a page, but one or two rows flow over onto the next page. I'd like to start a new page if the table won't fit onto the current one. I've tried some keep-with-previous tacks, but when a very long table won't fit onto a single page FOP errors out. Hi, keep-with-previous property doesn't work for table list (see [1]) And this is not yet done in FOP_TRUNK (see [2]) Does anyone have a sure-fire method for causing a table to start on a new page if all the rows won't fit on the current page? If you know rows height, you can add an explicit page break when needed, for example using the XPATH sequence position() mod XXX, where XXX is the number of rows per page. We use the position() mod XXX technique to break page sequences and release memory, but there is one major issue we always run in to: when a cell wraps and the row height increases, your row counts are now off and the breaks no longer occur at predicted intervals. This can be minimized if you have _very_ predictable data in your cells. -Lou Thanks. Charles Knell [1] http://xmlgraphics.apache.org/fop/knownissues.html [2] http://xmlgraphics.apache.org/fop/changes.html HTH, Pascal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Keeping tables together with FOP 0.92b
I know that if a table has 20 or more rows, it won't fit on a single page. I
deal with such large tables in my XSLT like this:
xsl:template match=table
xsl:variable name=page-break-flag
xsl:choose
xsl:when test=count(child::column) gt; 19page/xsl:when
xsl:otherwiseauto/xsl:otherwise
/xsl:choose
/xsl:variable
...
fo:table-row keep-with-next=always break-before={$page-break-flag}
fo:table-cellfo:block/fo:block/fo:table-cell
...
/xsl:template
Here I am dealing with a situation where the number of rows on a particular
table may not be very large, but because other tables appear on the page before
it, the page breaks in the middle of the table, like this.:
Page Break
Table 1
row
row
row
row
Table 2
row
row
row
row
row
row
row
row
Table 3
row
row
row
row
Page Break
row
row
row
row
Table 4
row
row
row
row
In my case, the row heights are always the same, so Louis' warning is not
applicable.
In order to know if I should start a new page before beginning to print Table
3, I would have to know the number of rows that already appear on the page (or
some other more clever work-around), but I can't think of a way to get that
information.
Does this suggest a solution to anyone?
Thanks.
--
Charles Knell
[EMAIL PROTECTED] - email
ÿþ
< b r > < f o n t s i z e = 2 > < t t > & q u o t ; P a s c a l S a n c h o & q u o t ; & l t ;[EMAIL PROTECTED]& g t ;
w r o t e o n 0 9 / 1 4 / 2 0 0 6 0 7 : 4 7 : 0 9 A M : < b r >
< b r >
& g t ; & g t ; - - - - - O r i g i n a l M e s s a g e - - - - - < b r >
& g t ; & g t ; F r o m : [EMAIL PROTECTED] [ m a i l t o :[EMAIL PROTECTED] < b r >
& g t ; & g t ; S e n t : W e d n e s d a y , S e p t e m b e r 1 3 , 2 0 0 6 9 : 1 5 P M < b r >
& g t ; & g t ; < b r >
& g t ; & g t ; I ' r e c e n t l y b a c k t o w o r k i n g w i t h F O P . I h a v e a d o c u m e n t t h a t
< b r >
& g t ; & g t ; c o n s i s t s o f a n u m b e r o f t a b l e s w i t h w i d e l y - v a r y i n g n u m b e r s o f
< b r >
& g t ; & g t ; r o w s . S o m e t i m e s s e v e r a l t a b l e s w i l l f i t e n t i r e l y o n t o a < b r >
& g t ; & g t ; s i n g l e p a g e , w i t h o t h e r s w i l l s p a n s e v e r a l p a g e s . T h e p r o b l e m
< b r >
& g t ; & g t ; I ' m h a v i n g i n v o l v e s t h o s e c a s e s w h e r e a t a b l e a l m o s t f i t s < b r >
& g t ; & g t ; o n t o a p a g e , b u t o n e o r t w o r o w s f l o w o v e r o n t o t h e n e x t < b r >
& g t ; & g t ; p a g e . I ' d l i k e t o s t a r t a n e w p a g e i f t h e t a b l e w o n ' t f i t < b r >
& g t ; & g t ; o n t o t h e c u r r e n t o n e . < b r >
& g t ; & g t ; < b r >
& g t ; & g t ; I ' v e t r i e d s o m e k e e p - w i t h - p r e v i o u s t a c k s , b u t w h e n a v e r y < b r >
& g t ; & g t ; l o n g t a b l e w o n ' t f i t o n t o a s i n g l e p a g e F O P e r r o r s o u t . < b r >
& g t ; < b r >
& g t ; H i , < b r >
& g t ; k e e p - w i t h - p r e v i o u s p r o p e r t y d o e s n ' t w o r k f o r t a b l e & a m p ; l i s t ( s e e
[ 1 ] ) < b r >
& g t ; A n d t h i s i s n o t y e t d o n e i n F O P _ T R U N K ( s e e [ 2 ] ) < b r >
& g t ; < b r >
& g t ; & g t ; D o e s a n y o n e h a v e a s u r e - f i r e m e t h o d f o r c a u s i n g a t a b l e t o < b r >
& g t ; & g t ; s t a r t o n a n e w p a g e i f a l l t h e r o w s w o n ' t f i t o n t h e c u r r e n t
p a g e ? < b r >
& g t ; < b r >
& g t ; I f y o u k n o w r o w s h e i g h t , y o u c a n a d d a n e x p l i c i t p a g e b r e a k w h e n n e e d e d , < b r >
& g t ; f o r e x a m p l e u s i n g t h e X P A T H s e q u e n c e & q u o t ; p o s i t i o n ( ) m o d X X X & q u o t ; ,
w h e r e X X X i s < b r >
& g t ; t h e n u m b e r o f r o w s p e r p a g e . < b r >
& g t ; < b r >
< / t t > < / f o n t >
< b r > < f o n t s i z e = 2 f a c e = " s a n s - s e r i f " > W e u s e t h e < / f o n t > < f o n t s i z e = 2 > < t t > & q u o t ; p o s i t i o n ( )
m o d X X X & q u o t ; < / t t > < / f o n t > < f o n t s i z e = 2 f a c e = " s a n s - s e r i f " > t e c h n i q u e t o b r e a k
p a g e s e q u e n c e s a n d r e l e a s e m e m o r y , b u t t h e r e i s o n e m a j o r i s s u e w e a l w a y s
r u n i n
RE: Keeping tables together.
THe
way I know to keep two differents elements (tables, images, etc...) is to put
them into a table and use the keep-with-next attribute on the "main" table
cells...
-
create a main table with 1 column and 2 rows
- put
your first table into the first cell of the main
table
- put
your second table into the second cell of the main table
- use
the keep-with-next or keep with previous attribute on the main
cells
De: Andre Groeneveld
[mailto:[EMAIL PROTECTED] Envoyé: lundi 6 mars 2006
10:03À: fop-users@xmlgraphics.apache.orgObjet:
Keeping tables together.
Hi all,
Is there a way of keeping two tables
together on the same page? The two tables are different in column sizes, the
first table has for example 2 columns and the second table has 5 or 6
columns.
Thanx,
Confidentiality Caution and Disclaimer
This message and/or any attachment thereto ("the message")contains
privileged and confidential information intendedonly for the recipient. If you are not the intended recipient of
this message,please erase it permanently once you have notified
thesender, per return e-mail, that you have received themessage in
error.Unless the sender is duly authorised by either the
TelesureGroup, or any of its subsidiary or affiliated companies or I.S Services("the Group") to send
this message and unless the contentof this message is also duly authorised
by the Group, anyviews expressed in this message are those of the
individualsender and the Group will not accept liability therefore,nor
for any consequential damage arising there from.Any recipient of an
unacceptable communication, a chainletter or offensive material of any
nature is requestedto be reported to [EMAIL PROTECTED].
