Hello Vincent, > > Well, most of the time even I would use the balancing algorithm, but not in > > all cases. I guess I could implement a kind of fox-useBalancer="false" > > for this cases, but even that would not make Block C (see below) possible.
> Well, I think it would. Basically the option would be "do not balance columns > before a block that spans the whole page". So, on your example below, the > bottom of page 1 is reached before block E is encountered, so columns are > balanced. On page 2, block E is encountered so column balancing is disabled, > then re-enabled after block E until the bottom of the page, etc. Actually > this would be more efficient since there would be no need to re-typeset the > content, in order to balance columns before a spanning block, as I believe > it's done ATM. Might be a useful extension. So it would be an extension for the page, not for the block. Either for simple-page-master or (probably better) for region-body, if I understand you correctly. Do you think that's possible and how much work would it be? Mind, I'm not asking you to implement it, but if you say it's possible and you could do it in a day, I guess I might be able to do it in a reasonable time (actually, not me, but a colleague of mine who actually knows his way around the fop source code, I hope). > > I don't mind the manual work (as long as it's the computer doing it), > > mostly I mind the manual splitting of one fo:block into one > > 2-column-block (or right column block) on one page and a second > > 1-column-block with margin on the second page, because the block could > > contain stuff like lists and that seems quite error-prone to me. > > > > keep-together.within-column would make the whole block move to the second > > column if there are two blocks before a wide block. > > Using a combination of keep-together="always" and > > keep-with-previous.within-column="always" works fine for the first page, > > but when breaking from > > page 1 to page 2, I would want a page break, maybe even a column break on > > page 1, but no column break on page 2 (Block C in this sketch): > My idea was to manually split block C, and surround the part of it that's on > the second page /and/ block D with another block that has a keep- > together.within-column setting. An alternative to the spanning block with a > big right margin, that might be easier to implement, but that won't avoid > you to manually split the content unfortunately. You are right, if I have to split the blocks anyway, I would not need the right margin. Regards, Georg Datterl ------ Kontakt ------ Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH: www.irs-nbg.de Willmy PrintMedia GmbH: www.willmy.de Willmy Consult & Content GmbH: www.willmycc.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
