FOP 0.20.5 ignores an empty table-body, no error message. XEP 4 displays a validation error and continues. AltSoft Xml2PDF does the same. FOP CVS HEAD now does the same.
The justifications for both changes are in the commit message. If you prefer a hard exception in the case of an empty table-body then add a flag on the user agent for strict vs. relaxed validation testing. As for removeChild(): Remove that method yourself and try to fix the layout managers. You'll quickly see that my fix is probably the cleanest and quickest solution for fixing the problem if we are to allow empty table-bodies. It removes the trouble maker before it can cause any problems in the layout engine. And: As for suggesting a change in the spec. I don't want that. 1. We have to cope with what we have: XSL 1.0. 2. Empty table-bodies make no sense but it makes life easier for stylesheet writers not to have to work around them. I have nothing more to say about this. I want to spend my time on more productive things now. On 24.02.2005 00:01:05 Glen Mazza wrote: > Jeremias, > > This should not be done. If someone has a problem > with it--and I've never heard a complaint--they can > send an email to xsl-editors, for them to adjust the > content model for fo:table accordingly. (If they > don't, they don't.) > > Note that the editors are very reasonable about > this--for example, fo:page-sequence-wrapper and > fo:wrapper are allowed to have no children for > programmatic convenience, even though it doesn't make > sense for these items to be empty. > > BTW, what is FONode.removeChild() for anyway? Why is > this helpful--we haven't needed such a method for > years. Jeremias Maerki
