https://issues.apache.org/bugzilla/show_bug.cgi?id=44412
--- Comment #23 from Vincent Hennebert <[EMAIL PROTECTED]> 2008-04-30 02:44:08 PST --- (In reply to comment #20) > Ok, there seems to be a tendency towards merging the breaks. I personally lean > towards not merging them. But we're a democracy. ;-) > > I just noticed one thing that might be speaking against merging the breaks: > <fo:block break-before="column"> > <fo:block break-before="page"> > Some text. Some text. Some text. Some text. > </fo:block> > </fo:block> > The spec definitely doesn't say anything about break conflicts, i.e. which > break "wins" in the above situation if they are to be merged. 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. Otherwise, Andreas’ comment #22 has a point. The idea is to generate as few breaks as necessary that still comply with all of the break specifications in the document. The only unsure thing is regarding borders (comment #4 vs comment #6), and I'll send a request for clarification on this soon. <snip/> Vincent -- 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.
