J.Pietschmann wrote:
Karen Lease wrote:A while back, if I remember correctly, someone was looking for and perhaps going to write an extension to write continued labels in table headers. Ie, when the table continues, to add text like "(continued)" or whatever in the header (and/or footer).
Apparently this never made it into the common pool, but I have recently cooked up something fairly simple (and limited) to handle this. Is there interest in putting it in for the next maintenance release ? It has very minor impact on the table layout code and probably would be useful to a number of people.
Well, the functionality can be nearly emulated with standard XSLFO, even though it is somewhat messy, and perhaps some unwanted space appears. Therefore it can be discussed whether this should go into the FOP code pool.
I needed this urgently for "real" work. The use of the static flow in this context would have been a real hack, whereas "continued" type functionality is a fairly standard part of real page layout systems. There were 2 or 3 positive responses to my message, so I put it in to the maintenance branch. As I wrote, it's quite limited, but at least now it's available for improvement, extension or integration in some larger context.
A more generalized functionality would be FO which are conditionally
rendered before/after page breaks in the FO which they are attached
to:
<fo:block>
<fox:before-page-break>
<fo:block>Continued on next page<fo:block>
</fox:before-page-break>
<fox:after-page-break>
<fo:block>Continued from previouss page<fo:block>
</fox:after-page-break>
bla bla bla...
Because there is now an EXSLFO initiative, I think we should supply
a draft spec there and wait for some consensus before making comminments
to the FOP code base (unless asked for proof-of-concept or something).
I'll take care if writing the spec and submitting it, right after
I've cleaned the backlog.
Is this ok?
Sounds fine to me, as long as you post your proposed spec here before posting it to EXSLFO. I think this functionality is most common in tables, but it can certainly be useful in a more general context. In any case, I already have a user request to do the opposite of "continued-label", ie: to compose some content only in the first area generated by an FO, and not in any remaining areas, so you might want to account for that as well.
This brings up a point: is this type of functionality aimed at first/non-first/last area generated by a given FO, or by an area on a page (as in your example)? Note that if there are several columns on a page, these are not necessarily the same.
Regards,
Karen
J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
