https://issues.apache.org/bugzilla/show_bug.cgi?id=44412
--- Comment #24 from Andreas L. Delmelle <[EMAIL PROTECTED]> 2008-04-30 08:33:17 PST --- (In reply to comment #23) > > Right. I took on me to implement a ‘conflict’ resolution in > o.a.f.util.BreakUtil#compareBreakClasses. In your example the final break > would > be a page break, since a page break also implies a column break. Hmm... Not sure I agree entirely. At any rate, this is one of those examples that demonstrates that it's actually not really a merge I'm thinking of. As stated in comment #21, I think it depends... The outer block's break-condition can be satisfied by a column-break. That should be the first effective break. Whether we need a second effective page-break depends on whether the column-break moves to a new column on the same page, or already coincides with a page-break. Only in the latter case, the result is identical to what is proposed above. Supposing a two-column layout: <fo:block>...</fo:block> <fo:block break-before="column" border="1pt solid red"> <fo:block break-before="page" border="0.5pt solid blue"> ... The result I'd expect would be: - content of the first block in page#1, column#1 - top border of the second (outer) block on page#1 (!), column#2 - third (inner) block on page#2 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
