https://issues.apache.org/bugzilla/show_bug.cgi?id=46905
--- Comment #18 from Chris Bowditch bowditch_ch...@hotmail.com 2009-06-04
00:37:12 PST ---
(In reply to comment #17)
(In reply to comment #16)
This won't work. If keep-together.within-column=1 and
keep-together.within-page=always
https://issues.apache.org/bugzilla/show_bug.cgi?id=47314
Summary: [PATCH] Suppress page breaks between page sequences
Product: Fop
Version: 0.95
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority:
Hi Ben,
Thank you very much for your interest in FOP and your contribution. I’ve
opened a Bugzilla issue containing your patch so that it can easily be
referred to:
https://issues.apache.org/bugzilla/show_bug.cgi?id=47314
It is likely to interest other users who run into similar memory issues,
Vincent -
I agree this is a work-around and does distort the semantics of the
fo:page-sequence element. When I opened up the FOP 0.95 Source last week, it
became apparent that trying to interject where FOP starts its layout would be
time consuming. Currently the handlers are directly tied to
https://issues.apache.org/bugzilla/show_bug.cgi?id=47314
Laera Dario lae...@ima.it changed:
What|Removed |Added
CC||lae...@ima.it
--
On Thu, Jun 04, 2009 at 11:35:17AM +0100, Vincent Hennebert wrote:
It is likely to interest other users who run into similar memory issues,
and the good thing of having made it against the 0.95 release is that it
won???t be made obsolete by further changes in the code.
We are not going to
On 04 Jun 2009, at 14:11, Simon Pepping wrote:
Hi Ben, Simon Vincent,
snip /
Indeed, it is a horrible hack with regard to the meaning of a
page-sequence. But it is an interesting solution to the problem of
influencing FOP's page breaking algorithm.
The very same thoughts over here. A
I agree that this should happen behind the scenes without the user
having to specify anything. I had to perform this work-around the way I
did because of our current time constraints. Hopefully, this can lead
to something else. Unfortunately, my knowledge of the Apache FOP Source
only extends to
On 04 Jun 2009, at 14:53, Ben Wuest wrote:
Hi Ben
I agree that this should happen behind the scenes without the user
having to specify anything. I had to perform this work-around the
way I
did because of our current time constraints. Hopefully, this can lead
to something else.
Hi Ben,
very good idea, I'm facing the same issue for very long report and your
solution may be helpful.
-Messaggio originale-
Da: Andreas Delmelle [mailto:andreas.delme...@telenet.be]
Inviato: giovedì 4 giugno 2009 14.35
A: fop-dev@xmlgraphics.apache.org
Oggetto: Re: Apache FOP
On 04 Jun 2009, at 15:36, Laera Dario wrote:
Hi Dario
I once ran a test with a document
containing one single fo:block with the pre-formatted text of an
entire book. Without 'linefeed-treatment=preserve', FOP needed at
least 768MB to avoid running out of memory, because it had to
recompute all
11 matches
Mail list logo
