Re: Problem with fo:marker and keep-with-next in tables

2003-04-22 Thread J.Pietschmann
Müller, Markus wrote:
We want to list some items on an invoice using a table. It is possible, that
not all items fit into a single page. So we allow following pages, but then
we have to print a carry over at the end and the beginning of each page. The
computation is not the problem, we do this by adding appropriate attributes
to the items' corresponding xml-elements. The carry over values then are
placed into markers. Additionaly, always 3 items (= fo:table-rows) are set
to keep together using keep-with-next="always". Doing so, retrieving the
markers fails (first-starting and last-ending). FOP returns a marker NEAR
the correct marker, sometimes even the correct one. This feature seams to be
nondeterministic.
This is quite deterministic. The problem is that there is an attempt
at laying out some rows, then a conflict with the keep condition is
detected and the layout is rolled back, almost. This particular
problem with not resetting markers during rollback should be fixed
in CVS (see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16999)
Other similar problems remain, for example with footnotes.
BTW, it seems that the markers' is_first / is_last attributes are set BEFORE
the keep-xxx directives are processed.
I think the flags are reset during the rollback. If not, well, yet
another bug.
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Problem with fo:marker and keep-with-next in tables

2003-04-22 Thread "Müller, Markus"
Hi *,

We want to list some items on an invoice using a table. It is possible, that
not all items fit into a single page. So we allow following pages, but then
we have to print a carry over at the end and the beginning of each page. The
computation is not the problem, we do this by adding appropriate attributes
to the items' corresponding xml-elements. The carry over values then are
placed into markers. Additionaly, always 3 items (= fo:table-rows) are set
to keep together using keep-with-next="always". Doing so, retrieving the
markers fails (first-starting and last-ending). FOP returns a marker NEAR
the correct marker, sometimes even the correct one. This feature seams to be
nondeterministic.

Jochen Unger asked the same question a few weeks ago, but there were no
answers in the mailing list. 

Is there a solution for this problem???

BTW, it seems that the markers' is_first / is_last attributes are set BEFORE
the keep-xxx directives are processed.

Markus  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Problem with fo:marker

2002-11-18 Thread Oleg Tkachenko
Yann Verlynde wrote:
I have some trouble with fo:marker. The String that I want to write on the
top of my page when my text in on 2 pages minimum does not work.
I see it on the first page but not on the second.
Does anyone can help me?
This is my code in my static-content
 



M

Here is a mistake -  object must have no content, 
it's just a counterpart of , which *retrieves* a marker value 
and therefore it doesn't have its own value.



F

The same mistake.
The main idea underneath is pretty simple - you define a marker of one 
class at your table cells, having content either M or ? and in static 
content you just retrieves the marker of this class.

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


Problem with fo:marker

2002-11-15 Thread Yann Verlynde
Hello,

I have some trouble with fo:marker. The String that I want to write on the
top of my page when my text in on 2 pages minimum does not work.
I see it on the first page but not on the second.
Does anyone can help me?

This is my code in my static-content








M













F







...

and in the body I use:















 





...