Jeremias Maerki wrote:

XSL 1.0, 6.4.19, fo:static-content says:


So you must at least have one block as a child for fo:static-content (It
can be empty). The redesigned FOP is much more strict about the
interpretation of the specification.

The reason why XSL is strict about this is to guard against XSLT errors--i.e., a erroneously un-activated XSLT template causing your fo:static-content element to be empty on (say) page 240, and you not knowing that because your XSL processor silently kept running (or just giving a warning message among several screens of other output.) By halting, it allows you to go back and fix the template error instead of submitting an erroneously built document to someone else.


To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to