Have you tried the Trunk version? I'm not sure what enhancements may
have been made, but I have seen someone mention problems with
keep-together attributes before.
Personally, I use FOP for reporting and I'm used to old style reporting
where I print everything explicitly line by line so I should know what
fits on a page. I don't bother making sure auto formatting works, I
just format it. I report data in XML with tags to specify what column
and row each piece of text should start and the maximum columns to fit
across the page. The XSL uses that to calculate the block and text
size. I force the location to make sure it fits on a page:
<fo:block-container>
<xsl:attribute name="position">absolute</xsl:attribute>
I don't know if forcing left, top, width, height attributes and
calculating font-size would work for you but I find it very cool.
-----Original Message-----
From: Michael Seeberger [mailto:[email protected]]
Sent: Wednesday, June 30, 2010 8:18 AM
To: [email protected]
Subject: Page-Break and keep-together.within-page
Hi there,
i'm using Apache-Fop Version 0.95 and i'm having problems to get my
report created the way i want it to.
The problem lies in the behaviour of Apache-FOP and the
"keep-together.within-page"-attribute.
The report i want to create consists of several fo:block-Elements in
which i use fo:table-elements to layout the report and the behaviour of
Apache-FOP as i want it to be should be something like
this:
Condition 1. if a fo:block fits completely on a page then it should
stay there.
Condition 2. if a fo:block won't fit completely on a page then
Apache-FOP should insert a page-break and print it on the next page (i
implemented this by using keep-together.within-page="always" and it
works).
Condition 3. if a fo:block is to large for a single page Apache-FOP
should insert a page-break where necessary (won't work if condition 2 is
implemented).
But until now i've not been able to get Apache-FOP working this way
because FOP seems to have a problem with the combination of condition 1
and condition 2. When a fo:block won't fit on a page FOP inserts a
page-break when using keep-together but if this fo:block is to large for
a single page it won't insert another page-break where necessary but
overflows the page.
The Reason for this seems to be the attribute-value "always", as my
Google-research tells me "always" means that when using this value an
fo:xxx-Element stays together no matter what even when this leads to an
overflow.
I've also tried using keep-together.with-next or
keep-together.with-previous but it didn't work either and using
integer-values instead of always isn't supported by Apache-FOP 0.95 as
far as i know.
And heres my Question: Is there really no way to make Apache-FOP create
the report the way i want it to?
thx in advance
Michael Seeberger
---------------------------------------------------------------------
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]