Dear Wiki user, You have subscribed to a wiki page or wiki category on "Xmlgraphics-fop Wiki" for change notification.
The "WhitespaceManagement" page has been changed by GlennAdams: https://wiki.apache.org/xmlgraphics-fop/WhitespaceManagement?action=diff&rev1=16&rev2=17 Comment: Add question about use of fo:multi-switch et al. }}} * As (in general) we could not know how many lines each alternative will create, we may need a way to define a priority between the alternative (a priority attribute?) so that, if both the n-th alternative and the m-th one lead to the creation of K lines the application knows which one to use. [LF] + * Instead of creating new extension element types, why not use fo:multi-switch and fo:multi-case (instead of the proposed fox:best-fit and fox:best-fit-alternative), along with a new extension property, fox:best-fit on fo:multi-switch, which triggers an implicit process for setting the currently-visible-multi-case trait on the fo:multi-switch to select none or one of the alternative fo:multi-case sub-trees to contribute generated areas? The structure and function of these existing FO element types exactly match the proposed new element types. [GA] + == Thoughts for a possible implementation == First thought is to implement it similarly to a block-container with stretch and shrink. The implementation could measure the min/opt/max of every alternative and could calculate a combined min/opt/max from that. Creating Knuth elements for this combined min/opt/max is easy (a single box plus glue for the whole best-fit block with no break opportunity in between). After the page breaking, generating the contents of a particular alternative is easy and can be done the same way as for block-container. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
