On Dec 14, 2007, at 01:59, Manuel Mall wrote:
Hi Manuel, Vincent,
Just a quick question coming from someone who has absolutely no
clue about
what you are really doing and just based on the commit comment.
We have been 'bitten' before by moving things into the fo tree only
to find
out that it doesn't work when it comes to fo:markers as they
inherit the
environment from where they are retrieved into not from where they
come
from. Is that possibly an issue here?
I too haven't looked very closely at Vincent's changes, but he did
manage to implement something that up to now, I have only speculated
to be possible, so I am VERY interested ;-)
There is already one certainty that should make things much more
straightforward here:
fo:tables in retrieved fo:markers can, by definition, not have any
page-breaks.
Since, as I recall, it should be possible to resolve/collapse /all/
borders in a table in the FO Tree, provided it does not span multiple
pages, I wouldn't suspect any problems here.
Borders are also not inherited, and IIC, it is not possible to put,
for example, separate fo:table-rows in fo:markers that will be
retrieved into a fo:table-body in a static-content.
But this is all theoretical, so up to Vincent to confirm...
Just my 2 cents.
Cheers
Andreas
