Keep-together
I saw some earlier postings on problems with keep-together when there are fo:blocks inside table rows but never saw an answer. It seems that when you have a table row with multiple fo:blocks then FOP allows it to break to the next page ignoring the keep-together. My table rows are all defined as: fo:table-row keep-with-previous=always keep-with-next=always My data contains tags to indicate line breaks (br/). My style sheet replaces all br/ tags with: fo:block space-before=13pt space-after=0pt xsl:apply-templates/ /fo:block If data inside a table containes any of these added fo:blocks then that row is allowed to break to the next page if necessary. I really need a way to keep the table together. FOP claims to support keep-togther in table rows but this behaviour seems to suggest table rows do not even work correctly (or am I doing something wrong?). Does anyone have any insight on this. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Keep-together
Steve Lockwood wrote: My table rows are all defined as: fo:table-row keep-with-previous=always keep-with-next=always You probably want to try fo:table-row keep-toghether=always J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bug with keep-together?
As FOP has keep-together implemented only for table rows I am formatting some content in a table. Now I have different margins for first page and rest of the pages. I have some content which has keep-together set to always and it should print on first page if it fits in its entirety or should start on second page. It does exactly that but the problem lies with the table width. I have set the table-width for this keep-together table to be 100%. I have 1in margins for all sides on first page and 0.5in margins for the rest of the pages. Now when the content is more than what can be accommodated on the remaining part of the first page, it prints to content on second page BUT it has 1.5 in margin on the right side. It is not exactly margin but the table width is calculated as 100% considering the 1in margins and so the rest of the space on the right side is left blank when this table is printed on the second page (0.5 in margin). I can say for sure that table width is calculated as per the first page because except for this table the content on second page has 0.5 in margin on all right and left sides. So is this a bug? Should I specify the table width something other than 100%? __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Addition: Bug with keep-together?
This is how I am formatting the table used to
implement Keep Together
fo:table width=100%
space-before={$ActualSpaceBefore}
table-layout=fixed
fo:table-column/
fo:table-body
fo:table-row keep-together=always
fo:table-cell
fo:block color={$FontColorBase}
line-height={$LineHeightBase}
xsl:apply-templates/
/fo:block
/fo:table-cell
/fo:table-row
/fo:table-body
/fo:table
__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bug with keep-together?
Abhijit Junnare wrote: As FOP has keep-together implemented only for table rows I am formatting some content in a table. Now I have different margins for first page and rest of the pages. I have some content which has keep-together set to always and it should print on first page if it fits in its entirety or should start on second page. It does exactly that but the problem lies with the table width. I have set the table-width for this keep-together table to be 100%. That's a bug with percentage resolution rather than with keep-toghether. The percentage is resolved with respect to the area where the table starts and is not recalculated if the table spills into an area with a different width. The same happens with basically all other percentages, including widths on comon blocks. You just have to avoid spreading blocks whose width involves calculating percentages over blocks with different area widths. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: keep together pages
Yes I must admit that using a transformer would be much straighter. But I'm handling with dynamic data and I want to have a table-layout. This would not work... thanx! -Ursprüngliche Nachricht- Von: Victor Mote [mailto:[EMAIL PROTECTED] Gesendet: Tuesday, August 19, 2003 4:24 PM An: [EMAIL PROTECTED] Betreff: RE: keep together pages Todtenhaupt, Susann wrote: I'm producing TXT through XSL:FO and FOP. If there're more than one page there's following effect: Between the pages there's a break of several lines. I didn't find a property to suppress this pagebreak. The TXT output is laid out on the page just as it would for PDF, then converted to text. I suspect that the blank lines are the layout's way of mimicking the margins at the top and bottom of a printed page. Try eliminating (or making very tiny) the regions and margins at the top and bottom of the page. See http://xml.apache.org/fop/output.html#txt for more details. Another alternative is to simply use an XSLT transformation to get your text output. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
keep together pages
Hi @ all! I'm producing TXT through XSL:FO and FOP. If there're more than one page there's following effect: Between the pages there's a break of several lines. I didn't find a property to suppress this pagebreak. Can anybody help me? Greetz and thanx suse! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: keep together pages
Todtenhaupt, Susann wrote: I'm producing TXT through XSL:FO and FOP. If there're more than one page there's following effect: Between the pages there's a break of several lines. I didn't find a property to suppress this pagebreak. The TXT output is laid out on the page just as it would for PDF, then converted to text. I suspect that the blank lines are the layout's way of mimicking the margins at the top and bottom of a printed page. Try eliminating (or making very tiny) the regions and margins at the top and bottom of the page. See http://xml.apache.org/fop/output.html#txt for more details. Another alternative is to simply use an XSLT transformation to get your text output. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FOP0.20.5rc and keep-together=retrieve-marker doesn't work corre ctly
Hi! I use two markers in a fo:table to retrieve sums for page header (region-before) and footer (region-end). for each account position ... table-row keep-together=always keep-together.within-page=always fo:table-cell fo:block text-align=center !--Marker -- fo:marker marker-class-name=subtotalvalue xsl:call-template name=soll_haben xsl:with-param name=textÜbertrag/xsl:with-param xsl:with-param name=amount xsl:choose xsl:when test=A_AMOUNT!='' xsl:value-of select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/TOTALSANDLIMITS/@A_SBALANCE+A_AMOU NT+sum(preceding::A_AMOUNT[.!=''])/ /xsl:when xsl:otherwise xsl:value-of select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/TOTALSANDLIMITS/@A_SBALANCE + sum(preceding::A_AMOUNT[.!= ''])/ /xsl:otherwise /xsl:choose /xsl:with-param xsl:with-param name=currency select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/ACCOUNTHEADER/@CURRENCY/ /xsl:call-template /fo:marker fo:marker marker-class-name=subtotalvalueEx xsl:call-template name=soll_haben xsl:with-param name=textÜbertrag/xsl:with-param xsl:with-param name=amount xsl:value-of select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/TOTALSANDLIMITS/@A_SBALANCE + sum(preceding::A_AMOUNT[.!= ''])/ /xsl:with-param xsl:with-param name=currency select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/ACCOUNTHEADER/@CURRENCY/ /xsl:call-template /fo:marker ... other output like A_AMOUNT ... To get the sum for the footer : fo:retrieve-marker retrieve-class-name=subtotalvalue retrieve-boundary=page retrieve-position=last-starting-within-page/ To get the sum for the header : fo:retrieve-marker retrieve-class-name=subtotalvalueEx retrieve-boundary=page retrieve-position=first-starting-within-page/ Some accountpositions have payment-notes, that are added as additional table-rows : fo:table-row xsl:attribute name=keep-with-previous.within-pagealways/xsl:attribute xsl:attribute name=keep-with-previousalways/xsl:attribute ... payment - note ... What happened is that FOP keeps blocks correctly together. (Accountposition and payment-notes should not be on separate pages) But fo:retrieve-marker sometimes fetches wrong values (from previous / following lines). As a result the sum on a page and their following may differ. Is that behavior a ( known ) mistake ? Regards Joachim Unger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FOP0.20.5rc and keep-together=retrieve-marker doesn't work corre ctly
Hi! I use two markers in a fo:table to retrieve sums for page header (region-before) and footer (region-end). for each account position ... table-row keep-together=always keep-together.within-page=always fo:table-cell fo:block text-align=center !--Marker -- fo:marker marker-class-name=subtotalvalue xsl:call-template name=soll_haben xsl:with-param name=textÜbertrag/xsl:with-param xsl:with-param name=amount xsl:choose xsl:when test=A_AMOUNT!='' xsl:value-of select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/TOTALSANDLIMITS/@A_SBALANCE+A_AMOU NT+sum(preceding::A_AMOUNT[.!=''])/ /xsl:when xsl:otherwise xsl:value-of select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/TOTALSANDLIMITS/@A_SBALANCE + sum(preceding::A_AMOUNT[.!= ''])/ /xsl:otherwise /xsl:choose /xsl:with-param xsl:with-param name=currency select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/ACCOUNTHEADER/@CURRENCY/ /xsl:call-template /fo:marker fo:marker marker-class-name=subtotalvalueEx xsl:call-template name=soll_haben xsl:with-param name=textÜbertrag/xsl:with-param xsl:with-param name=amount xsl:value-of select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/TOTALSANDLIMITS/@A_SBALANCE + sum(preceding::A_AMOUNT[.!= ''])/ /xsl:with-param xsl:with-param name=currency select=/ACCOUNTDOCUMENT/ACCOUNTSTATEMENT/ACCOUNTHEADER/@CURRENCY/ /xsl:call-template /fo:marker ... other output like A_AMOUNT ... To get the sum for the footer : fo:retrieve-marker retrieve-class-name=subtotalvalue retrieve-boundary=page retrieve-position=last-starting-within-page/ To get the sum for the header : fo:retrieve-marker retrieve-class-name=subtotalvalueEx retrieve-boundary=page retrieve-position=first-starting-within-page/ Some accountpositions have payment-notes, that are added as additional table-rows : fo:table-row xsl:attribute name=keep-with-previous.within-pagealways/xsl:attribute xsl:attribute name=keep-with-previousalways/xsl:attribute ... payment - note ... What happened is that FOP keeps blocks correctly together. (Accountposition and payment-notes should not be on separate pages) But fo:retrieve-marker sometimes fetches wrong values (from previous / following lines). As a result the sum on a page and their following may differ. Is that behavior a ( known ) mistake ? Regards Joachim Unger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep-together / blind tables
On Monday 03 March 2003 19:31, Peter Solberg wrote: Try the :fo:table-header There are other examples in the FOP package.. However, if you want running headers such as fo:retrieve-marker, you cannot use this... you must put the fo:retrieve-marker in xsl:region-before. This helps. Thanks! -Matthias Brunner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: keep-together / blind tables
Let's try this code (I did not test it): substitute: fo:table-row fo:table-cell xsl:apply-templates select=paragraph/ /fo:table-cell /fo:table-row through: xsl:for-each select=paragraph fo:table-row fo:table-cell fo:blockxsl:value-of select=././fo:block /fo:table-cell /fo:table-row /xsl:for-each -Ursprüngliche Nachricht- Von: Matthias Brunner [SMTP:[EMAIL PROTECTED] Gesendet am: Montag, 3. März 2003 19:25 An: [EMAIL PROTECTED] Betreff: keep-together / blind tables Hello, I know this is a FAQ but I did not find anything appropriate to my specific problem. I have paragraphs with a heading and, of course, I do not want the heading to be left alone on one page with the paragraphs being on the next one. ---excerpt--- xsl:template match=paragraphs fo:table table-layout=fixed width=100% fo:table-column column-width=proportional-column-width(1)/ fo:table-body fo:table-row keep-with-next=always fo:table-cell xsl:apply-templates select=heading/ /fo:table-cell /fo:table-row fo:table-row fo:table-cell xsl:apply-templates select=paragraph/ /fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template ---excerpt--- keep-with-next works, the heading is never left alone. But even if a paragraph is half a page in size it is not seperated any more thus leaving ugly blank spots on the pages. (strange ASCII art example attached below :) What can I do to allow the separation of this paragraph? Thanks in advance, Matthias Example: p1 heading/ paragraph content content content /paragraph EMPTY EMPTY EMPTY EMPTY --- p2 heading/ paragraph content content content content content content content /paragraph INSTEAD OF: p1 heading/ paragraph content content content /paragraph heading/ paragraph content content- --- p2 content content content content content /paragraph EMPTY EMPTY EMPTY EMPTY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
keep-together / blind tables
Hello, I know this is a FAQ but I did not find anything appropriate to my specific problem. I have paragraphs with a heading and, of course, I do not want the heading to be left alone on one page with the paragraphs being on the next one. ---excerpt--- xsl:template match=paragraphs fo:table table-layout=fixed width=100% fo:table-column column-width=proportional-column-width(1)/ fo:table-body fo:table-row keep-with-next=always fo:table-cell xsl:apply-templates select=heading/ /fo:table-cell /fo:table-row fo:table-row fo:table-cell xsl:apply-templates select=paragraph/ /fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template ---excerpt--- keep-with-next works, the heading is never left alone. But even if a paragraph is half a page in size it is not seperated any more thus leaving ugly blank spots on the pages. (strange ASCII art example attached below :) What can I do to allow the separation of this paragraph? Thanks in advance, Matthias Example: p1 heading/ paragraph content content content /paragraph EMPTY EMPTY EMPTY EMPTY --- p2 heading/ paragraph content content content content content content content /paragraph INSTEAD OF: p1 heading/ paragraph content content content /paragraph heading/ paragraph content content- --- p2 content content content content content /paragraph EMPTY EMPTY EMPTY EMPTY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep-together / blind tables
Try the :fo:table-header There are other examples in the FOP package.. However, if you want running headers such as fo:retrieve-marker, you cannot use this... you must put the fo:retrieve-marker in xsl:region-before. Does that help? Pete Solberg xsl:template match="paragraphs"fo:table table-layout="fixed" width="100%" fo:table-column column-width="proportional-column-width(1)"/fo:table-header fo:table-row fo:table-cell xsl:apply-templates select="heading"/ /fo:table-cell /fo:table-row/fo:table-header fo:table-body fo:table-row fo:table-cell xsl:apply-templates select="paragraph"/ /fo:table-cell /fo:table-row /fo:table-body/fo:table/xsl:template From: Matthias Brunner <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: keep-together / blind tables Date: Mon, 3 Mar 2003 19:24:35 +0100 Hello, I know this is a FAQ but I did not find anything appropriate to my specific problem. I have paragraphs with a heading and, of course, I do not want the heading to be left alone on one page with the paragraphs being on the next one. ---excerpt--- ---excerpt--- keep-with-next works, the heading is never left alone. But even if a paragraph is half a page in size it is not seperated any more thus leaving ugly blank spots on the pages. (strange ASCII art example attached below :) What can I do to allow the separation of this paragraph? Thanks in advance, Matthias Example: p1 content content content EMPTY EMPTY EMPTY EMPTY --- p2 content content content content content content content INSTEAD OF: p1 content content content content content- --- p2 content content content content content EMPTY EMPTY EMPTY EMPTY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The new MSN 8: smart spam protection and 2 months FREE* - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: keep-together in a multi-column document
Thibodeaux, Paul wrote: I'm using FOP to build a multi-column, multipage document that is essentially a directory of sorts, with names, addresses, and phone numbers. I'd like to keep all the lines of each entry together in the same column, but keep-together.within-column on the parent block doesn't seem to be working to do this for me. It seems to be ignored. Does anyone have any ideas on this? You need to use fo:region-body column-count=3/ (or 4 or 2 or 5 etc.) Here's a sample for a dictionary or directory which uses markers for the page headings etc. Chuck fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=page-first page-height=8.5in page-width=11in fo:region-body margin-top=5cm margin-bottom=.5in margin-left=.5in margin-right=.5in column-count=3/ fo:region-before extent=6cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=page-first fo:static-content flow-name=xsl-region-before fo:table table-layout=fixed fo:table-column column-width=5.5in/ fo:table-column column-width=5.5in/ fo:table-body fo:table-row fo:table-cell fo:block keep-together=auto first-starting-within-page: fo:retrieve-marker retrieve-class-name=entry retrieve-boundary=page retrieve-position=first-starting-within-page/ /fo:block /fo:table-cell fo:table-cell fo:block keep-together=auto text-align=end first-including-carryover : fo:retrieve-marker retrieve-class-name=entry retrieve-boundary=page retrieve-position=first-including-carryover/ /fo:block /fo:table-cell /fo:table-row fo:table-row fo:table-cell fo:block keep-together=auto last-starting-within-page : fo:retrieve-marker retrieve-class-name=entry retrieve-boundary=page retrieve-position=last-starting-within-page/ /fo:block /fo:table-cell fo:table-cell fo:block keep-together=auto text-align=end last-ending-within-page : fo:retrieve-marker retrieve-class-name=entry retrieve-boundary=page retrieve-position=last-ending-within-page/ /fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:static-content fo:flow flow-name=xsl-region-body fo:blockfo:marker marker-class-name=entryOne/fo:markerOne One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One One fo:marker marker-class-name=entryOnex/fo:marker/fo:block fo:blockfo:marker marker-class-name=entryTwo/fo:markerTwo Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two Two fo:marker marker-class-name=entryTwox/fo:marker/fo:block fo:blockfo:marker marker-class-name=entryThr/fo:markerThr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr Thr fo:marker marker-class-name=entryThrx/fo:marker/fo:block fo:blockfo:marker marker-class-name=entryFou/fo:markerFou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou Fou fo:marker marker-class-name=entryFoux/fo:marker/fo:block fo:blockfo:marker marker-class-name=entryFiv/fo:markerFiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv Fiv fo:marker marker-class-name=entryFivx/fo:marker/fo:block fo:blockfo:marker marker-class-name=entrySix/fo:markerSix Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six Six fo:marker marker-class-name=entrySixx/fo:marker/fo:block fo:blockfo:marker marker-class-name=entrySev/fo:markerSev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev Sev
Is there any alternative to the Keep-together property
As we all know, the following properties still don't work with fop 0.20.3: keep-together keep-with-previous keep-with-next Is there any solution to do it another way ? Does someone knowwhen will these functions be implemented in FOP ? Thank you Stéphane
AW: Is there any alternative to the Keep-together property
You know the workaround with fo:table-row keep-with-previous="always" keep-with-next="always", i guess. -Ursprüngliche Nachricht-Von: Stéphane REYNIER [mailto:[EMAIL PROTECTED]Gesendet: Donnerstag, 25. April 2002 15:40An: Mailing list FOPBetreff: Is there any alternative to the "Keep-together" property As we all know, the following properties still don't work with fop 0.20.3: keep-together keep-with-previous keep-with-next Is there any solution to do it another way ? Does someone knowwhen will these functions be implemented in FOP ? Thank you Stéphane
Re: to J.Pietschmann (about keep-together)
J.Pietschmann [EMAIL PROTECTED]: MARTIN Franck wrote: Thank you for your advice but what do you mean by blind table? A table without borders, so you don't notice it's actually there. Often used for doing complicated layouts which can be fitted manually to an underlying grid. In your case, just for keeping stuff together. I have a similar problem. My problem is that my FO is generated from DocBook source, and that the only way I can see how to accomplish a blind table, is to create a different template for DocBook section elements that will create a mess for regular sections. Hm...
AW: Again: keep-together
Hello Chuck, thank you for replying. Unfortunately I failed to express myself clearly. Maybe since there are different problems playing together in that case. My point is that we do not see how to proceed by using tables for getting the two column formatting that our customer would have liked: We have those two column stuff alternating with one column parts. The two column parts consist of fairly complex (ie. nested) tables of vary varying length. The tables have to be splitted so that the left and right column are as balanced as possible, i.e. their length are as matching as possible. Counting lines and splitting after a half does not help. Beside being rather involved, since the lines are tables and pictures themselves and do not have constant height. The only way we have found to do at least a rough approximation of equally long columns with fop was to use the two columned layout and NOT a two columned table. Are wrong? Thanks again, Frank -Ursprüngliche Nachricht- Von: Chuck Paussa [mailto:[EMAIL PROTECTED] Gesendet am: Donnerstag, 18. April 2002 19:12 An: [EMAIL PROTECTED] Betreff: Re: Again: keep-together Frank, H I'm not exactly sure what you're trying for but, here's some suggestions: Use fo:table-cell number-columns-spanned=2 for the cell that has the 1 column header Use the fo:region-before fo:static-content area to hold what would look like the regular table header that is printed on each page and then break up each of the tables with those 1 column headers into separate tables with the one column header on the fo:table-header area (That way, if the table happens to break across a page boundary, the table header is repeated on the next page.) Chuck Paussa Nestel, Frank ISC 6 wrote: I know you all work hard. But just to express priority. We are currently stuck with a problem we cannot see how to cope without working keep properties. Or can anybody give me some help on how to achive below layout with fop. 1.one-column header 2.two-column table two-column table column1 column2 1.one-column header 2.two-column table two-column table column1 column2 1.one-column header 2.two-column table two-column table column1 column2 ... above pattern repeats very often... ... tables of varying length with very variable height of single rows ... We are using the two columns to get the variable length table no. 2 balanced between left and right side (which BTW does not work to well, the left hand side gets way to long). I do not see how to achieve this effect with a table, since I have absolute no means to measure the where to break the table into into two parts. We have long headers over the tables and those header have to kept close to their table. I know how to do it with TeX, but this ain't help :-) But its funny to run in this kind of problem over 20 years after TeX was programmed. Best regards, Frank Nestel -Ursprüngliche Nachricht- Von: J.Pietschmann [mailto:[EMAIL PROTECTED] MARTIN Franck wrote: Does anyone know of a way to prevent blocks or tables from being divided when a page break occurs? Is the property keep-together implemented in fop? The keep-together property is not yet implemented, and it will take a while until it is. The keep-with-next and keep-with-previous properties work on table rows only. If block elements should be kept together, you can put them into a one-column blind table. HTH J.Pietschmann
Re: AW: Again: keep-together
Frank, OK, that makes sense. You want to have a headline and then sanking columns underneath, like in a newspaper. Headline Goes here This is the after the information headline that goes balanced. New headline here This is the after the information headline that goes balanced. I tried a whole bunch of stuff using the column-count attribute of region-body (which is the only way I know to create snaking columns.) Region-body is the only element with a column-count attribute (right?) And I couldn't get it to work. The basic idea would be to wrap two blocks in a block or block-container with a span=all fo:block-container height=15mm width=190mm top=0mm left=0mm position=absolute border=solid 1px pink span=all fo:block span=all Here's a headline #1 that should cross all the way across the page /fo:block fo:block span=none Now is the time for all good men to come to the aid of their country. Now is the time for all good men to come to the aid of their country. Now is the time for all good men to come to the aid of their country. Now is the time for all good men to come to the aid of their country. Now is the time for all good men to come to the aid of their country. Now is the time for all good men to come to the aid of their country. /fo:block /fo:block-container But, that doesn't work. The inner blocks are not aware of the columns in the region containing them. There have been a number of problems like this that I have not found an automated way to address and so have been forced to pre-calculate the page layout of each page and then absolutely position the contents on the page. For fo: processed documents, that looks like the only way to go for now unless someone else can chime in with a solution I haven't seen yet. Chuck Nestel, Frank ISC 6 wrote: Hello Chuck, thank you for replying. Unfortunately I failed to express myself clearly. Maybe since there are different problems playing together in that case. My point is that we do not see how to proceed by using tables for getting the two column formatting that our customer would have liked: We have those two column stuff alternating with one column parts. The two column parts consist of fairly complex (ie. nested) tables of vary varying length. The tables have to be splitted so that the left and right column are as balanced as possible, i.e. their length are as matching as possible. Counting lines and splitting after a half does not help. Beside being rather involved, since the lines are tables and pictures themselves and do not have constant height. The only way we have found to do at least a rough approximation of equally long columns with fop was to use the two columned layout and NOT a two columned table. Are wrong? Thanks again, Frank -Ursprüngliche Nachricht- Von: Chuck Paussa [mailto:[EMAIL PROTECTED] Gesendet am: Donnerstag, 18. April 2002 19:12 An: [EMAIL PROTECTED] Betreff: Re: Again: keep-together Frank, H I'm not exactly sure what you're trying for but, here's some suggestions: Use fo:table-cell number-columns-spanned=2 for the cell that has the 1 column header Use the fo:region-before fo:static-content area to hold what would look like the regular table header that is printed on each page and then break up each of the tables with those 1 column headers into separate tables with the one column header on the fo:table-header area (That way, if the table happens to break across a page boundary, the table header is repeated on the next page.) Chuck Paussa Nestel, Frank ISC 6 wrote: I know you all work hard. But just to express priority. We are currently stuck with a problem we cannot see how to cope without working keep properties. Or can anybody give me some help on how to achive below layout with fop. 1.one-column header 2.two-column table two-column table column1 column2 1.one-column header 2.two-column table two-column table column1 column2 1.one-column header 2.two-column table two-column table column1 column2 ... above pattern repeats very often... ... tables of varying length with very variable height of single rows ... We are using the two columns to get the variable length table no. 2 balanced between left and right side (which BTW does not work to well, the left hand side gets way to long). I do not see how to achieve this effect with a table, since I have absolute no means to measure the where to break the table into into two parts. We have long headers over the tables and those header have to kept close to their table. I know how to do it with TeX, but this ain't help :-) But its funny to run in this kind of problem over 20 years after TeX was programmed. Best regards, Frank Nestel -Ursprüngliche Nachricht- Von: J.Pietschmann [mailto
Re: to J.Pietschmann (about keep-together)
MARTIN Franck wrote: Thank you for your advice but what do you mean by blind table? A table without borders, so you don't notice it's actually there. Often used for doing complicated layouts which can be fitted manually to an underlying grid. In your case, just for keeping stuff together. J.Pietschmann
to J.Pietschmann (about keep-together)
If block elements should be kept together, you can put them into a one-column blind table. Thank you for your advice but what do you mean by blind table? Franck MARTIN
keep-together
Hi Does anyone know of a way to prevent blocks or tables from being divided when a page break occurs? Is the property keep-together implemented in fop? Thanx Franck MARTIN
How to use keep-together?
Hi, Sorry to bother you all again. This should be the last question for a while. I've been trying to get keep-together=always to work. I've tried it on blocks, inlines and on blocks surrounding blocks. Nothing seems to make any difference, yet the FOP parser doesn't complain about the code. Again, I just want to know whether it's me or FOP. This would be a very nice feature to have implimented in FOP. It *does* seem to be in the pdf documentation that came with FOP. Just for completeness, here's some code I'm trying. block keep-together=always space-after=0.5emThis is a test with keep-together inline keep-together=always Indignor quicquam reprehendi, non quia crasse compositum illepedeve putetur, sed quia nuper, nec veniam antiquis, sed honorem et praemia posci. Recte necne crocum floresque perambulet Attae fabula si dubitem, clament periisse pudorem cuncti paene patres, ea cum reprehendere coner, quae gravis Aesopus, quae doctus Roscius egit; vel quia nil rectum, nisi quod placuit sibi, ducunt, vel quia turpe putant parere minoribus, et quae imberbes senes. /inline /block It just carries on splitting regardless. ( Any ideas? -- Best, Stephen
