DO NOT REPLY [Bug 7241] - keep-with-previous, keep-with-next only working on the first page break
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241 keep-with-previous, keep-with-next only working on the first page break --- Additional Comments From [EMAIL PROTECTED] 2002-12-20 22:10 --- I have exactly the same problem: works first page break, doesn't work second page break -- didn't try consecutive page breaks, but I assume same as Bernd says. RedHat Linux 8.0, Fop 0.20.4. Added myself as CC and changed OS to "All" (I assume that's the case), I'd be interested to keep posted on this problem. thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: orphan/window control, blind tables, keep-with-next etc
Eddy De Clercq wrote: Hi, I've seen in the archives in the FOP mailing list lots of threads concerning this matter. Is there any news/update on when features like orphan/widow control, keep-with-next will be implemented in FOP (and Cocoon)? Eddy, Wait for about a day, then see what Sun has come up with. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ "Lord, to whom shall we go?" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
orphan/window control, blind tables, keep-with-next etc
Hi, I've seen in the archives in the FOP mailing list lots of threads concerning this matter. Is there any news/update on when features like orphan/widow control, keep-with-next will be implemented in FOP (and Cocoon)? Many thanks Eddy De Clercq
DO NOT REPLY [Bug 7241] - keep-with-previous, keep-with-next only working on the first page break
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241 keep-with-previous, keep-with-next only working on the first page break [EMAIL PROTECTED] changed: What|Removed |Added Version|0.20.3 |0.20.4 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7241] - keep-with-previous, keep-with-next only working on the first page break
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241 keep-with-previous, keep-with-next only working on the first page break --- Additional Comments From [EMAIL PROTECTED] 2002-11-21 12:55 --- Created an attachment (id=3909) Testcase (Version 0.20.4) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7241] - keep-with-previous, keep-with-next only working on the first page break
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241 keep-with-previous, keep-with-next only working on the first page break --- Additional Comments From [EMAIL PROTECTED] 2002-11-20 13:18 --- Provide an example please (fo document, add it as attachment). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
keep-with-previous problem
HI Devs, I'm trying to keep a set of rows in a table together with keep's in the table-rows. But somehow, I'm not able to get it. I have attached the FO file, I'm using. Opening it in the AWT viewer shows 3 pages with a remnant in the 2nd page. Actually, with the FO written, it has to be moved to the 3rd page. Please, help. Ramana. temp.fo Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5434] - keep-with-next, keep-with-previous do not work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434 keep-with-next, keep-with-previous do not work [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 08:54 --- *** This bug has been marked as a duplicate of 3044 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 1432] - keep-with-* not functioning for fo:table-row
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1432>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1432 keep-with-* not functioning for fo:table-row [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Priority||High Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 07:46 --- The changes seem to have been applied to the source. It works in the current FOP version 0.20.0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 7241] New: - keep-with-previous, keep-with-next only working on the first page break
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7241 keep-with-previous, keep-with-next only working on the first page break Summary: keep-with-previous, keep-with-next only working on the first page break Product: Fop Version: 0.20.3 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have a large table, using about 8 pages. Some rows (about every 4th) has the keep-with-previous="always". On the first page-break this works fine. The following page breaks ignore the keep-with-previous. The same is for the keep-with-next. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: problems with keep-with-next
Stephen Bannasch <[EMAIL PROTECTED]> wrote: > keep-with-next still doesn't work on 0.20.3 It is implemented only for table rows. > The problem is very annoying when I have a figure > with a title on one page and the image on the next. Put stuff that should be kept together in a one column blind table and use keep-with-next on the rows. Be careful, overdoing this could send FOP into an unterminating loop. Please post followup questions on fop-user. HTH J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: problems with keep-with-next
Isn't it true that keep-with-next is still only implemented for the table-row element? -Matt Stephen Bannasch wrote: > > keep-with-next still doesn't work on 0.20.3 > > I tried to add a comment to: > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434 > > but i couldn't figure out how (probably too late at night :-) > > Anyway there is a very simple test case here: > > http://concord.org/~stephen/fop-bugs/keep-with-next-bug.fo > > the testcase keep-with-next-bug.fo references the image: > > http://concord.org/~stephen/fop-bugs/ccprobe-interface-blockdiag.png > > The problem is very annoying when I have a figure with a title on one page and the >image on the next. > > -- > > -s > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
problems with keep-with-next
keep-with-next still doesn't work on 0.20.3 I tried to add a comment to: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434 but i couldn't figure out how (probably too late at night :-) Anyway there is a very simple test case here: http://concord.org/~stephen/fop-bugs/keep-with-next-bug.fo the testcase keep-with-next-bug.fo references the image: http://concord.org/~stephen/fop-bugs/ccprobe-interface-blockdiag.png The problem is very annoying when I have a figure with a title on one page and the image on the next. -- -s - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5434] - keep-with-next, keep-with-previous do not work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434 keep-with-next, keep-with-previous do not work --- Additional Comments From [EMAIL PROTECTED] 2002-02-21 17:24 --- This is still broken with fop-0.20.3rc2-src.tar.gz. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5099] - fop gets stuck in infinite loop when table rows with "keep-with-next" that together, are larger than the current page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5099>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5099 fop gets stuck in infinite loop when table rows with "keep-with-next" that together, are larger than the current page [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-02-11 12:21 --- Fixed in 0.20.3rc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AW: keep-with-next?
Thank you for your response! I was afraid you would say this. :) I was hoping it might be a relatively simple fix; I wonder if there isn't a kluge I can put in the existing approach that would suffice for the heading/following paragraph problem... So FOP is basically being redesigned/rewritten, eh? I wonder how far along this is. On Thu, 31 Jan 2002, Bertrand Delacretaz wrote: > (by the way your message was crossposted to fop-user, please avoid this as it > makes it very hard to follow discussions) > > On Wednesday 30 January 2002 20:21, David Wood wrote: > > I am a Java coder and know my way around the standard. I volunteer to try > > to fix this, if someone who is more familiar with FOP's internals can > > tell me where to look... > > I cannot help you much, but here's at least a reply to your offer ;-) > > AFAIK getting keep-with... stuff to work requires serious redesign, which is > currently going on (Keiron and Karen?), but apparently fairly slowly. > > Keiron would probably be the one to answer you, but in his last message > (Jan.14th I think) he indicated that he'd be "away for some time". I have no > idea when he will be back, maybe someone knows more? > > -- > -- Bertrand Delacrétaz, www.codeconsult.ch > -- web technologies consultant - OO, Java, XML, C++ > > > > > > > - > 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: AW: keep-with-next?
(by the way your message was crossposted to fop-user, please avoid this as it makes it very hard to follow discussions) On Wednesday 30 January 2002 20:21, David Wood wrote: > I am a Java coder and know my way around the standard. I volunteer to try > to fix this, if someone who is more familiar with FOP's internals can > tell me where to look... I cannot help you much, but here's at least a reply to your offer ;-) AFAIK getting keep-with... stuff to work requires serious redesign, which is currently going on (Keiron and Karen?), but apparently fairly slowly. Keiron would probably be the one to answer you, but in his last message (Jan.14th I think) he indicated that he'd be "away for some time". I have no idea when he will be back, maybe someone knows more? -- -- Bertrand Delacrétaz, www.codeconsult.ch -- web technologies consultant - OO, Java, XML, C++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: AW: keep-with-next?
I should be more specific - what I mean is; I would like to try to get keep-with-next/previous working with fo:block elements. On Wed, 30 Jan 2002, David Wood wrote: > I am a Java coder and know my way around the standard. I volunteer to try > to fix this, if someone who is more familiar with FOP's internals can > tell me where to look... > > -David > > On Wed, 30 Jan 2002, Sam Prokop wrote: > > > I found out it just works with table-rows, if you use keep-with-next and > > keep-with-previous. > > and you have to take care, that the table doesn´t exceeds the page, > > otherwise you´ll get a infinite-loop. > > > > that´s all i found out :-( > > > > Sam > > > > > -Ursprüngliche Nachricht- > > > Von: Costantino Sertorio [mailto:[EMAIL PROTECTED]] > > > Gesendet: Montag, 28. Januar 2002 16:51 > > > An: [EMAIL PROTECTED] > > > Betreff: keep-with-next? > > > > > > > > > Hello, > > > Is the keep-with-next attribute supported by FOP? > > > If yes, can anybody explain to me what I am doing wrong? > > > I have a "heading" template which I would like to keep > > > together with the > > > following text, therefore I defined the following, but it > > > doesn't work (the > > > following paragraph ends up in the next page): > > > > > > > > > > > > > > > > > space-before="0.6cm" space-after > > > ="0.6cm" font-size="13pt" font-weight="bold"> > > > > > > > > > > > > > > > > > font-size=" > > > 10pt" font-weight="bold"> > > > > > > > > > > > > > > > Thank you, > > > > > > Costantino > > > > > > > > > > > > > > > - > 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: AW: keep-with-next?
I am a Java coder and know my way around the standard. I volunteer to try to fix this, if someone who is more familiar with FOP's internals can tell me where to look... -David On Wed, 30 Jan 2002, Sam Prokop wrote: > I found out it just works with table-rows, if you use keep-with-next and > keep-with-previous. > and you have to take care, that the table doesn´t exceeds the page, > otherwise you´ll get a infinite-loop. > > that´s all i found out :-( > > Sam > > > -Ursprüngliche Nachricht- > > Von: Costantino Sertorio [mailto:[EMAIL PROTECTED]] > > Gesendet: Montag, 28. Januar 2002 16:51 > > An: [EMAIL PROTECTED] > > Betreff: keep-with-next? > > > > > > Hello, > > Is the keep-with-next attribute supported by FOP? > > If yes, can anybody explain to me what I am doing wrong? > > I have a "heading" template which I would like to keep > > together with the > > following text, therefore I defined the following, but it > > doesn't work (the > > following paragraph ends up in the next page): > > > > > > > > > > > space-before="0.6cm" space-after > > ="0.6cm" font-size="13pt" font-weight="bold"> > > > > > > > > > > > font-size=" > > 10pt" font-weight="bold"> > > > > > > > > > > Thank you, > > > > Costantino > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5434] - keep-with-next, keep-with-previous do not work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434 keep-with-next, keep-with-previous do not work --- Additional Comments From [EMAIL PROTECTED] 2002-01-29 06:58 --- The same with FOP-0.20.3RC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5434] - keep-with-next, keep-with-previous do not work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434 keep-with-next, keep-with-previous do not work --- Additional Comments From [EMAIL PROTECTED] 2001-12-14 08:33 --- Created an attachment (id=901) Test fo file showing keep-with-next problems. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5434] New: - keep-with-next, keep-with-previous do not work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5434 keep-with-next, keep-with-previous do not work Summary: keep-with-next, keep-with-previous do not work Product: Fop Version: all Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] keep-with-next and keep-with-previous do not work. See the attached test file, which has several blocks of text that use keep-with-next. I tested on Fop-0.20.2RC-src.tar.gz running on RH 7.2 linux on a pentium. The output of the keep-with-next blocks is split across pages. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Keep-with-next - what is the plan
Sorry if this has been asked before I just joined this mailing list, I was on the xsl:fo mailing list before this. Hello all, I've been using FOP for some time now and I was wondering does anyone know when "keep-with-next" will be fixed. FOP (xsl:fo) is so cool but my VP is always saying why can't this title and this image stay on the same page? Maybe someone knows a work around?? Thanks, Jay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5099] New: - fop gets stuck in infinite loop when table rows with "keep-with-next" that together, are larger than the current page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5099>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5099
fop gets stuck in infinite loop when table rows with "keep-with-next" that together,
are larger than the current page
Summary: fop gets stuck in infinite loop when table rows with
"keep-with-next" that together, are larger than the
current page
Product: Fop
Version: all
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: pdf renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
this may not be a bug, but this is similar the the problem of having an image
that is larger than the page (a description of the infinite-loop-on-large-
images bug can be found at this link:
http://www.owal.co.uk:8090/asf/servlet/asf/screen/DisplayQuestionAnswer/action/S
etAll/project_id/18/faq_id/276/topic_id/495/question_id/788
)
An infinite loop occurs when:
you have a group of table rows that are always supposed to be kept together,
but this group is larger than the page. table rows are kept together when they
have their "keep-with-previous" or "keep-with-next" property set to "always".
you would think that if you have a group of rows that are kept together that
are larger than the page, you should just remove one of the "keep-with-
previous" properties from one of the rows. but, when fo docs are dynamically
generated from a DB, this isn't always possible. it seems like fo should know
to break the grouped rows itself.
here is my fo document that loops infinitely when rendered:
thanks in advance for any reponses to this bug,
peter joh
http://www.w3.org/1999/XSL/Format";>
C6C042 -
Regular Cab
OPTIONAL EQUIPMENT
S=Standard A=Available
W/A=Will Advise N/C=No
Charge
2003 Order Guide for
C6C042 Regular Cab
Published
Page
REAR TIRES
RE: keep-with-next, orphans, widows
It's my understanding, that right now keep-with-next is only implemented on the table-row element. What's more, you can only use it when you know you will not have any more rows than will fit on a page. Otherwise FOP goes into an endless loop. > -Original Message- > From: Jörg Flotho [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 26, 2001 5:33 AM > To: [EMAIL PROTECTED] > Subject: keep-with-next, orphans, widows > > > text-indent="0.0pt" line-height="1.2" orphans="1" widows="1"> > > > > > > what's wrong with this? > there is no result, whatever which parameter is given in > orphans ans widows. > > The next problem is keep-with-next: >space-before="5.0pt" > text-align="left" text-indent="0.0pt" > keep-with-next="true"> >font-size="11pt" font-weight="bold" > font-style="italic"> > > > > It doesn't work either. > > Can anyone help please? > > Jörg > > > - > 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: keep-with-next, orphans, widows
keep-with-next is implemented only for tables. Take a look at docs\html-docs\implemented.html under the FOP home directory to find out what is implemented. Regards, Mike -Original Message- From: Jörg Flotho [mailto:[EMAIL PROTECTED]] Sent: 26. november 2001 14:33 To: [EMAIL PROTECTED] Subject: keep-with-next, orphans, widows what's wrong with this? there is no result, whatever which parameter is given in orphans ans widows. The next problem is keep-with-next: It doesn't work either. Can anyone help please? Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
keep-with-next, orphans, widows
what's wrong with this? there is no result, whatever which parameter is given in orphans ans widows. The next problem is keep-with-next: It doesn't work either. Can anyone help please? Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: keep-with-next?
keep-with-previous is also implemented. You are right regarding the infinite loop. I have worked around this problem by estimating the number of rows in my table, and if it larger than a page (in my case 54 rows) I first output a page-brake and then build the table without using the keep-with-next attribute. Regards, Mike -Original Message- From: Savino, Matt C [mailto:[EMAIL PROTECTED]] Sent: 19. november 2001 23:30 To: '[EMAIL PROTECTED]' Subject: keep-with-next? It's my understanding that keep-with-next="always" at the row level is the only keep-="*" property currently implemented in FOP. Is this true? I've also noticed that if the number of rows included is too big to fit on one page, you get an endless loop. This makes keep-with-next unusable for me in 90% of the places where I would like to use it. Are there any solutions I'm overlooking here? Thanks a lot, -Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
keep-with-next?
It's my understanding that keep-with-next="always" at the row level is the only keep-="*" property currently implemented in FOP. Is this true? I've also noticed that if the number of rows included is too big to fit on one page, you get an endless loop. This makes keep-with-next unusable for me in 90% of the places where I would like to use it. Are there any solutions I'm overlooking here? Thanks a lot, -Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
keep-with....
Hi is there any timeline for the implementation of the 'keep-with-next' and 'keep-with-previous' properties for a fo:block object? i know that this is already working for table-rows but my layout would become to heavyweighted using tables for all my paragraphs. thanx daniel = Daniel Pfuhl mailto:[EMAIL PROTECTED] __ Do You Yahoo!? Gesendet von Yahoo! Mail - http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Keep with next
hi, afaik this should work for keeping together table-rows. so you maybe try to make something like this +---+ | header | row1 +---+ | | | paragraph | row2 | | +---+ so you will be able to keep row1 together with row2. hth daniel --- Raj <[EMAIL PROTECTED]> schrieb: > I need to keep paragraph headings together with the > paragraphs. As I understand from another mail this > is not implemented in fop yet. Any idea when this is > likely to be implemented? > Thanks > -Rajendran > = Daniel Pfuhl mailto:[EMAIL PROTECTED] __ Do You Yahoo!? Gesendet von Yahoo! Mail - http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Keep with next
I need to keep paragraph headings together with the paragraphs. As I understand from another mail this is not implemented in fop yet. Any idea when this is likely to be implemented? Thanks -Rajendran
Re: keep-with-next problem on multi column text
Keep in mind that attempting to implement keeps this way is essentially a stopgap measure. It is quite unlikely that the code will be useable for all situations and will most likely be replaced. As you outlined below there are a number of issues that make the current implementation complicated and will eventually lead to complex unmaintainable code. As far as the project is concerned it would be better to implement these things properly with a good plan on how to approach it from scratch. On the other hand it may be useful to have some small part implement for your needs and give you a chance to know how the code works. On Thu, 30 Aug 2001 19:46:21 Don Wellington wrote: > I was looking at rollback, and it didn't seem to undo > layouts. Instead I set up a Vector in FOnode to > contain a list of areas that a node creates, then > filled in FONode.removeAreas() to remove the areas > using that list. Then, I changed block to add the > area it creates to that list. Then, set the marker to > a value that will cause areas to be recreated, but not > do anything to IDs (couldn't figure out how to back > out ID's so didn't worry about it). The algorithm I > see for keep-with-next: > > A node layout returns keep-with-next > Set flag active for keep-with-next(page or column) > Attempt to layout next node > If next node layout returns AREA_FULL_NONE > determine if full area is a page or a column > If full area match with-(page/column) > remove areas created by previous node > set marker to prior to layout of previous node (I > think I have remove doing this.) > Return AREA_FULL_SOME > > Seems fairly simple. Here are the gotchas. > 1) Preventing infinite loops. If you have both areas > combined overflow the column of page, then it is > impossible to keep-with-next. > 2) I think a marker needs to be enumerated for setup > done no area created. Say AREAS_READY_TO_BE_CREATED = > -42, or possibly 0, since block uses the marker to > designate which subnodes have been created so far. > Basically, I think the use of marker needs to be > fomalized somewhat. > 3) Does undoing areas cause problems with the ID code? > If so, how do we undo IDs too? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: keep-with-next problem on multi column text
Hi Bodo- First, I don't think I qualify as better overlooking FOP, since my one and only contribution is getting that list-item thing to do what I wanted. But, here are some things I found out during that process, and answered below: --- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi Don, Arved > i would be greatfull to work with someone on a > related problem, who > better overlooks FOP then i do at the moment . > right now i have some questions: > > 1. i do not fully understand about the numerical and > symbolic values for > the keep-* stuff. > the standard says (in "4.8 Keeps and Breaks") that > there is any interger > value allowed which specify the "strength", whereas > higher number means > more strength is imposed on the keep condition. in > other words the > bigger the values is the more the fo-processor > should try to keep the > stuff together, right? but there are in addition > to symbolic values > "auto" (which means no keep condition) and "always" > (which means " keep > always ") . > on the other hand in FOP "always" is mapped to "5" > in fop and "auto" > is mapped to "7". > which would mean only the values 5,6 and 7 are > meaningfull and moreover > it looks as if the always should actually at least > be greater then "auto". > could you help me reducing my confusion? Maybe it would be easiest to just start with binary, either attempt to keep-with-next, or don't attempt. That might be a simpler case than trying to figure out how to define the various levels of keepness. To me it seems that would be most cases because either you can keep-with-next, or you can't because the keeped parts would overflow the column or page. That is a bug in what I did because overflow would cause an infinite loop. > 2. i'm unsure about the "within-*" (e.g. > "within-page") property > refinement. > if for example, i have a block with > keep-with-next.within-page="always" but > keep-with-next.within-column="auto" > does this mean that i should make a page break > before that block if > normaly the pagebreak would occure after it. but i > should not start new > column before that block instead let occure the > column break after this > block as if no keep-with-next property would have > been set, right? I was focused on the keep-with-next.within-page, so I am not really familiar with column handling. > 3. i don't yet understand how the mechanics of the > FONode.rollback() > works. it seems it has something to do with undoing > layout operations in > order to redoing this part of the layout with eg. > different column or > page breaks (e.g. if a keep condition occured that > could not be > fulfilled). am i on the right trak here? do you any > more details on > that, or do i need just to look more deeply in to > the source? I was looking at rollback, and it didn't seem to undo layouts. Instead I set up a Vector in FOnode to contain a list of areas that a node creates, then filled in FONode.removeAreas() to remove the areas using that list. Then, I changed block to add the area it creates to that list. Then, set the marker to a value that will cause areas to be recreated, but not do anything to IDs (couldn't figure out how to back out ID's so didn't worry about it). The algorithm I see for keep-with-next: A node layout returns keep-with-next Set flag active for keep-with-next(page or column) Attempt to layout next node If next node layout returns AREA_FULL_NONE determine if full area is a page or a column If full area match with-(page/column) remove areas created by previous node set marker to prior to layout of previous node (I think I have remove doing this.) Return AREA_FULL_SOME Seems fairly simple. Here are the gotchas. 1) Preventing infinite loops. If you have both areas combined overflow the column of page, then it is impossible to keep-with-next. 2) I think a marker needs to be enumerated for setup done no area created. Say AREAS_READY_TO_BE_CREATED = -42, or possibly 0, since block uses the marker to designate which subnodes have been created so far. Basically, I think the use of marker needs to be fomalized somewhat. 3) Does undoing areas cause problems with the ID code? If so, how do we undo IDs too? I hope that helps Bodo. Don > Bodo __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: keep-with-next problem on multi column text
Hi Arved-
I didn't get any reply that the patch was comitted,
and I am stuck behind a firewall that doesn't allow IP
tunneling. So, I don't have access to the CVS
repository.
Don
--- Arved Sandstrom <[EMAIL PROTECTED]> wrote:
> Sure, absolutely, I'll help out as a resource.
>
> Did your patch get committed? If not I'll take care
> of it. Sorry I'm a bit
> scattered...work is intense right now.
>
> Regards,
> Arved
>
> At 09:03 AM 8/29/01 -0700, you wrote:
> >Hi Arved-
> >
> >I submitted patches against 20.1 to do an effective
> >keep-with-next on list-item-label and
> list-item-body,
> >except I assumed an implied keep-with-next on
> >list-item-label. I would be glad to work with bodo
> on
> >this time permitting. It would probably be best,
> so
> >that there are not two different pieces of code
> >floating around doing nearly the same thing.
> >
> >Don
> >
> >--- Arved Sandstrom <[EMAIL PROTECTED]>
> wrote:
> >> Hi, Bodo
> >>
> >> I'd be very happy to help. I'm badly sidelined
> due
> >> to work pressure, but
> >> there is always some time I can pry loose...I'd
> >> rather spend that time
> >> getting new developers up to speed.
> >>
> >> I'll review the source this evening and give you
> a
> >> synopsis of what we are
> >> facing here.
> >>
> >> Regards,
> >> Arved Sandstrom
> >>
> >> At 12:18 PM 8/27/01 +0200, [EMAIL PROTECTED]
> wrote:
> >> >hi,
> >> >i tried to use the keep-with-next property on a
> >> multi column page with
> >> >some text blocks that normally fits on one
> page
> >> with 4 columns.
> >> >my text consists of this sequence of text
> blocks:
> >> every 2nd block is
> >> >meant to be a headline and the the following
> block
> >> is the paragraph
> >> >belonging to that headline.
> >> >therefore i set the keep-with-next attribute on
> the
> >> headline blocks but
> >> >still the column break occurred between the
> >> headline and the paragraph.
> >> >
> >> >looking in to the code i found that in
> >> >org.apache.fop.fo.flow.Block.layout(Area) the
> line:
> >> >this.keepWithNext =
> >> >
> >> this.properties.get("keep-with-next").getEnum();
> >> >
> >> >does not have any effect , since the getEnum()
> >> method always returns (0)
> >> >because the
> >> >org.apache.fop.fo.KeepProperty(Keep) does not
> >> overwrite the getEnum()
> >> >method.
> >> >
> >> >so i patched this so that this.keepWithNext got
> the
> >> value="5" (just to
> >> >see what will happen then ) but immediately i
> run
> >> in to another error:
> >> >the headline appeared on the bottom of the old
> >> column, a wrong page
> >> >break occurred (instead of a column break)
> >> >and the same headline appeared on the top of the
> >> new page.
> >> >
> >> >if nobody else is currently working on this
> >> problems i would be willing
> >> >to do this, if i (as a someone who just started
> to
> >> try to understand the
> >> >fop source code) get some assistance from the
> fop
> >> gurus.
> >> >
> >> >would you appreciate this?
> >> >
> >> >bodo teichmann
> >> >
> >> >
> >> >
> >> >
> >>
>
>>-
> >> >To unsubscribe, e-mail:
> >> [EMAIL PROTECTED]
> >> >For additional commands, email:
> >> [EMAIL PROTECTED]
> >> >
> >> >
> >> 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]
> >>
> >
> >
> >__
> >Do You Yahoo!?
> >Make international calls for as low as $.04/minute
> with Yahoo! Messenger
> >http://phonecard.yahoo.com/
> >
>
>-
> >To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> >For additional commands, email:
> [EMAIL PROTECTED]
> >
> >
> 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]
>
__
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: keep-with-next problem on multi column text
Hi Don, Arved
i would be greatfull to work with someone on a related problem, who
better overlooks FOP then i do at the moment .
right now i have some questions:
1. i do not fully understand about the numerical and symbolic values for
the keep-* stuff.
the standard says (in "4.8 Keeps and Breaks") that there is any interger
value allowed which specify the "strength", whereas higher number means
more strength is imposed on the keep condition. in other words the
bigger the values is the more the fo-processor should try to keep the
stuff together, right? but there are in addition to symbolic values
"auto" (which means no keep condition) and "always" (which means " keep
always ") .
on the other hand in FOP "always" is mapped to "5" in fop and "auto"
is mapped to "7".
which would mean only the values 5,6 and 7 are meaningfull and moreover
it looks as if the always should actually at least be greater then "auto".
could you help me reducing my confusion?
2. i'm unsure about the "within-*" (e.g. "within-page") property
refinement.
if for example, i have a block with
keep-with-next.within-page="always" but
keep-with-next.within-column="auto"
does this mean that i should make a page break before that block if
normaly the pagebreak would occure after it. but i should not start new
column before that block instead let occure the column break after this
block as if no keep-with-next property would have been set, right?
3. i don't yet understand how the mechanics of the FONode.rollback()
works. it seems it has something to do with undoing layout operations in
order to redoing this part of the layout with eg. different column or
page breaks (e.g. if a keep condition occured that could not be
fulfilled). am i on the right trak here? do you any more details on
that, or do i need just to look more deeply in to the source?
Bodo
Don Wellington wrote:
>Hi Arved-
>
>I submitted patches against 20.1 to do an effective
>keep-with-next on list-item-label and list-item-body,
>except I assumed an implied keep-with-next on
>list-item-label. I would be glad to work with bodo on
>this time permitting. It would probably be best, so
>that there are not two different pieces of code
>floating around doing nearly the same thing.
>
>Don
>
>--- Arved Sandstrom <[EMAIL PROTECTED]> wrote:
>
>>Hi, Bodo
>>
>>I'd be very happy to help. I'm badly sidelined due
>>to work pressure, but
>>there is always some time I can pry loose...I'd
>>rather spend that time
>>getting new developers up to speed.
>>
>>I'll review the source this evening and give you a
>>synopsis of what we are
>>facing here.
>>
>>Regards,
>>Arved Sandstrom
>>
>>At 12:18 PM 8/27/01 +0200, [EMAIL PROTECTED] wrote:
>>
>>>hi,
>>>i tried to use the keep-with-next property on a
>>>
>>multi column page with
>>
>>>some text blocks that normally fits on one page
>>>
>>with 4 columns.
>>
>>>my text consists of this sequence of text blocks:
>>>
>>every 2nd block is
>>
>>>meant to be a headline and the the following block
>>>
>>is the paragraph
>>
>>>belonging to that headline.
>>>therefore i set the keep-with-next attribute on the
>>>
>>headline blocks but
>>
>>>still the column break occurred between the
>>>
>>headline and the paragraph.
>>
>>>looking in to the code i found that in
>>>org.apache.fop.fo.flow.Block.layout(Area) the line:
>>>this.keepWithNext =
>>>
>>>
>>this.properties.get("keep-with-next").getEnum();
>>
>>>does not have any effect , since the getEnum()
>>>
>>method always returns (0)
>>
>>>because the
>>>org.apache.fop.fo.KeepProperty(Keep) does not
>>>
>>overwrite the getEnum()
>>
>>>method.
>>>
>>>so i patched this so that this.keepWithNext got the
>>>
>>value="5" (just to
>>
>>>see what will happen then ) but immediately i run
>>>
>>in to another error:
>>
>>>the headline appeared on the bottom of the old
>>>
>>column, a wrong page
>>
>>>break occurred (instead of a column break)
>>>and the same headline appeared on the top of the
>>>
>>new page.
>>
>>>if nobody else is currently working on this
>>>
>>problems i would be willing
>>
>>>to do this, if i (as a so
Re: keep-with-next problem on multi column text
Sure, absolutely, I'll help out as a resource.
Did your patch get committed? If not I'll take care of it. Sorry I'm a bit
scattered...work is intense right now.
Regards,
Arved
At 09:03 AM 8/29/01 -0700, you wrote:
>Hi Arved-
>
>I submitted patches against 20.1 to do an effective
>keep-with-next on list-item-label and list-item-body,
>except I assumed an implied keep-with-next on
>list-item-label. I would be glad to work with bodo on
>this time permitting. It would probably be best, so
>that there are not two different pieces of code
>floating around doing nearly the same thing.
>
>Don
>
>--- Arved Sandstrom <[EMAIL PROTECTED]> wrote:
>> Hi, Bodo
>>
>> I'd be very happy to help. I'm badly sidelined due
>> to work pressure, but
>> there is always some time I can pry loose...I'd
>> rather spend that time
>> getting new developers up to speed.
>>
>> I'll review the source this evening and give you a
>> synopsis of what we are
>> facing here.
>>
>> Regards,
>> Arved Sandstrom
>>
>> At 12:18 PM 8/27/01 +0200, [EMAIL PROTECTED] wrote:
>> >hi,
>> >i tried to use the keep-with-next property on a
>> multi column page with
>> >some text blocks that normally fits on one page
>> with 4 columns.
>> >my text consists of this sequence of text blocks:
>> every 2nd block is
>> >meant to be a headline and the the following block
>> is the paragraph
>> >belonging to that headline.
>> >therefore i set the keep-with-next attribute on the
>> headline blocks but
>> >still the column break occurred between the
>> headline and the paragraph.
>> >
>> >looking in to the code i found that in
>> >org.apache.fop.fo.flow.Block.layout(Area) the line:
>> >this.keepWithNext =
>> >
>> this.properties.get("keep-with-next").getEnum();
>> >
>> >does not have any effect , since the getEnum()
>> method always returns (0)
>> >because the
>> >org.apache.fop.fo.KeepProperty(Keep) does not
>> overwrite the getEnum()
>> >method.
>> >
>> >so i patched this so that this.keepWithNext got the
>> value="5" (just to
>> >see what will happen then ) but immediately i run
>> in to another error:
>> >the headline appeared on the bottom of the old
>> column, a wrong page
>> >break occurred (instead of a column break)
>> >and the same headline appeared on the top of the
>> new page.
>> >
>> >if nobody else is currently working on this
>> problems i would be willing
>> >to do this, if i (as a someone who just started to
>> try to understand the
>> >fop source code) get some assistance from the fop
>> gurus.
>> >
>> >would you appreciate this?
>> >
>> >bodo teichmann
>> >
>> >
>> >
>> >
>>
>>-
>> >To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> >For additional commands, email:
>> [EMAIL PROTECTED]
>> >
>> >
>> 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]
>>
>
>
>__
>Do You Yahoo!?
>Make international calls for as low as $.04/minute with Yahoo! Messenger
>http://phonecard.yahoo.com/
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, email: [EMAIL PROTECTED]
>
>
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: keep-with-next problem on multi column text
Hi Arved-
I submitted patches against 20.1 to do an effective
keep-with-next on list-item-label and list-item-body,
except I assumed an implied keep-with-next on
list-item-label. I would be glad to work with bodo on
this time permitting. It would probably be best, so
that there are not two different pieces of code
floating around doing nearly the same thing.
Don
--- Arved Sandstrom <[EMAIL PROTECTED]> wrote:
> Hi, Bodo
>
> I'd be very happy to help. I'm badly sidelined due
> to work pressure, but
> there is always some time I can pry loose...I'd
> rather spend that time
> getting new developers up to speed.
>
> I'll review the source this evening and give you a
> synopsis of what we are
> facing here.
>
> Regards,
> Arved Sandstrom
>
> At 12:18 PM 8/27/01 +0200, [EMAIL PROTECTED] wrote:
> >hi,
> >i tried to use the keep-with-next property on a
> multi column page with
> >some text blocks that normally fits on one page
> with 4 columns.
> >my text consists of this sequence of text blocks:
> every 2nd block is
> >meant to be a headline and the the following block
> is the paragraph
> >belonging to that headline.
> >therefore i set the keep-with-next attribute on the
> headline blocks but
> >still the column break occurred between the
> headline and the paragraph.
> >
> >looking in to the code i found that in
> >org.apache.fop.fo.flow.Block.layout(Area) the line:
> >this.keepWithNext =
> >
> this.properties.get("keep-with-next").getEnum();
> >
> >does not have any effect , since the getEnum()
> method always returns (0)
> >because the
> >org.apache.fop.fo.KeepProperty(Keep) does not
> overwrite the getEnum()
> >method.
> >
> >so i patched this so that this.keepWithNext got the
> value="5" (just to
> >see what will happen then ) but immediately i run
> in to another error:
> >the headline appeared on the bottom of the old
> column, a wrong page
> >break occurred (instead of a column break)
> >and the same headline appeared on the top of the
> new page.
> >
> >if nobody else is currently working on this
> problems i would be willing
> >to do this, if i (as a someone who just started to
> try to understand the
> >fop source code) get some assistance from the fop
> gurus.
> >
> >would you appreciate this?
> >
> >bodo teichmann
> >
> >
> >
> >
>
>-
> >To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> >For additional commands, email:
> [EMAIL PROTECTED]
> >
> >
> 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]
>
__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: keep-with-next problem on multi column text
Hi, Bodo
I'd be very happy to help. I'm badly sidelined due to work pressure, but
there is always some time I can pry loose...I'd rather spend that time
getting new developers up to speed.
I'll review the source this evening and give you a synopsis of what we are
facing here.
Regards,
Arved Sandstrom
At 12:18 PM 8/27/01 +0200, [EMAIL PROTECTED] wrote:
>hi,
>i tried to use the keep-with-next property on a multi column page with
>some text blocks that normally fits on one page with 4 columns.
>my text consists of this sequence of text blocks: every 2nd block is
>meant to be a headline and the the following block is the paragraph
>belonging to that headline.
>therefore i set the keep-with-next attribute on the headline blocks but
>still the column break occurred between the headline and the paragraph.
>
>looking in to the code i found that in
>org.apache.fop.fo.flow.Block.layout(Area) the line:
>this.keepWithNext =
>this.properties.get("keep-with-next").getEnum();
>
>does not have any effect , since the getEnum() method always returns (0)
>because the
>org.apache.fop.fo.KeepProperty(Keep) does not overwrite the getEnum()
>method.
>
>so i patched this so that this.keepWithNext got the value="5" (just to
>see what will happen then ) but immediately i run in to another error:
>the headline appeared on the bottom of the old column, a wrong page
>break occurred (instead of a column break)
>and the same headline appeared on the top of the new page.
>
>if nobody else is currently working on this problems i would be willing
>to do this, if i (as a someone who just started to try to understand the
>fop source code) get some assistance from the fop gurus.
>
>would you appreciate this?
>
>bodo teichmann
>
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, email: [EMAIL PROTECTED]
>
>
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]
keep-with-next problem on multi column text
hi,
i tried to use the keep-with-next property on a multi column page with
some text blocks that normally fits on one page with 4 columns.
my text consists of this sequence of text blocks: every 2nd block is
meant to be a headline and the the following block is the paragraph
belonging to that headline.
therefore i set the keep-with-next attribute on the headline blocks but
still the column break occurred between the headline and the paragraph.
looking in to the code i found that in
org.apache.fop.fo.flow.Block.layout(Area) the line:
this.keepWithNext =
this.properties.get("keep-with-next").getEnum();
does not have any effect , since the getEnum() method always returns (0)
because the
org.apache.fop.fo.KeepProperty(Keep) does not overwrite the getEnum()
method.
so i patched this so that this.keepWithNext got the value="5" (just to
see what will happen then ) but immediately i run in to another error:
the headline appeared on the bottom of the old column, a wrong page
break occurred (instead of a column break)
and the same headline appeared on the top of the new page.
if nobody else is currently working on this problems i would be willing
to do this, if i (as a someone who just started to try to understand the
fop source code) get some assistance from the fop gurus.
would you appreciate this?
bodo teichmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: keep-with-*
Hi Looking at: http://xml.apache.org/fop/implemented.html only keep-with-next is implemented, but is also listed as broken. As for keep-together and keep-with-previous these are not listed which means that they are not yet implemented. Sorry Regards Mads - Original Message - From: "GALLO Jean-Claude" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 30, 2001 5:04 PM Subject: keep-with-* > I am testing keep-with-next, keep-together, keep-with-previous. I'm using > them with fo:block, but it seems they don't work. Nothing appear in the > limitations page or the features page (except keep-with-next highlighted by > "(broken)"). > > IMHO they don't work, but AMI true ? > > > Thanks > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
keep-with-*
I am testing keep-with-next, keep-together, keep-with-previous. I'm using them with fo:block, but it seems they don't work. Nothing appear in the limitations page or the features page (except keep-with-next highlighted by "(broken)"). IMHO they don't work, but AMI true ? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Problem with 'display-align' and 'keep-with-next' on fo:table-row
Hi all, First up, I discovered this problem using the CVS version of FOP last updated about 2001-07-25 02:00 UTC. I have a table of about 4 columns and two sorts of rows. The first type is a heading row with all four cells containing text (or an image) of different heights with display-align="after". The second row type is (surprise, surprise) a details row and of rather variable length. As I want to have the heading printed with the details (of course), I set keep-with-next="always" on the heading fo:table-row. The problem is when this causes the head row to be moved to the top of the new page, the display-align settings have been reset, or ignored, or something. This is especially exacerbated when I have bottom borders on the heading row as they are "all over the place" :-) I can probably knock up a demonstration FO file if it's required. TTFN Struan Judd <*> "And so it begins ..." ICQ: 4498196 http://neongraal.sf.org.nz mailto:[EMAIL PROTECTED] Voicemail and Fax: +1 (201) 305-1011 x1006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
keep-with-next,keep,break etc etc
All, I have been watching the fop-dev dist list for a while now and there is an ever increasing number of requests for keep and break conditions to be fixed / summarised. To the point where I am totally confused about what works / doesnt / will do in x.xx version etc etc. Hopefully someone can answer the following questions just to clear things up a bit (read: can we have more than just "broken" written on the fop site) : - What works and what doesnt / with which versions ? - What is the relative importance of fixing it all up ? Hopefully I am not the only one that thinks if this was fixed then a Fop 1.0 production sticker could (almost) be stuck on the box. Help ! Daryl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Keep-with-previous
Falk wrote: > > Hello, > i've got the following list where I included the keep-with-previous="always" > directive in order to prevent > the list from beeing split at the end of the page. However the list does get > split at the end of the page. > Are there any other directives I could use ? AFAIK keep-with-previous is not implement for lists, but tables should support it, so you could try to use a non visible table for the formatting. > Thanks a lot ! > Falk Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Keep-with-previous
Hello, i've got the following list where I included the keep-with-previous="always" directive in order to prevent the list from beeing split at the end of the page. However the list does get split at the end of the page. Are there any other directives I could use ? Remark:a Thanks a lot ! Falk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Is keep-with-* working in fo:tables?
Hi Steven,
The specific problem mentioned in Bug 1432 has been corrected since
then, but I'm not sure it was done before 0.18.1. I just did a few tests
with the current CVS and the keep properties seem to be working
correctly for table-rows. I do notice that when there is not
keep-withs-* on all the rows, FOP actually breaks within a row rather
than between rows, which is not so great. But that's a different
problem. I attached a test file so you can check it out.
HTH,
Karen Lease
"Olivieri, Steven" wrote:
>
> Can someone please answer this?
>
> I see that Bug 1432 (regarding keep-with-* not working in fo:tables in 0.17)
> is still assigned a high priority. I'm using 0.18.1, and I believe it's not
> working in that version either. Was the bug fixed (and perhaps I'm doing
> something wrong), or is it still open?
>
> On my first row, I'm using keep-with-next="always" (inside my fo:table-row
> tag). With each row after that, I'm using both keep-with-next="always" and
> keep-with-previous="always." On the last row, I'm using
> keep-with-previous="always" (only). Is this the correct way to do it?
> The grouping is not that large, but I'm noticing that say for example the
> group is comprised of 4 rows. The rows are being split after 1 or 2 rows.
> My hope was that the group would move together to the next page.
>
> thanks in advance for any help.
>
> Regards,
> Steve Olivieri
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
http://www.w3.org/1999/XSL/Format";>
table examples
Page
Test keep-with-next, keep-with-previous on all tables rows.
the whole table should be pushed to the next page
Table 1: keep-with-next="always" on all rows except last and
keep-with-previous="always" on all rows except first
first row which has keep-with-next set to always
first row second column
first row in third column
second row which has both keep-with-next and keep-with-previous set to
always
second column
last column
third row which has both keep-with-next and keep-with-previous set to
always
second column
last column
fourth and last row which has keep-with-previous set to always
second column
last column
Test keep-with-next, keep-with-previous on some tables rows.
The table should be broken if FOP works as I think it does.
Table 2: keep-with-next="always" on first and second row
no keep-with constraints on the third and fourth rows
first row which has keep-with-next set to always
first row second column
first row in third column
second row which has both keep-with-next and keep-with-previous set to
always
second column
last column
third row which has neither keep-with-next nor keep-with-previous
properties
second column
last column
Is keep-with-* working in fo:tables?
Can someone please answer this? I see that Bug 1432 (regarding keep-with-* not working in fo:tables in 0.17) is still assigned a high priority. I'm using 0.18.1, and I believe it's not working in that version either. Was the bug fixed (and perhaps I'm doing something wrong), or is it still open? On my first row, I'm using keep-with-next="always" (inside my fo:table-row tag). With each row after that, I'm using both keep-with-next="always" and keep-with-previous="always." On the last row, I'm using keep-with-previous="always" (only). Is this the correct way to do it? The grouping is not that large, but I'm noticing that say for example the group is comprised of 4 rows. The rows are being split after 1 or 2 rows. My hope was that the group would move together to the next page. thanks in advance for any help. Regards, Steve Olivieri - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
