[xep-support] Re: [error] no space for an element, trying to recover

On 12 February 2011 23:44, Kevin Brown <kevin@renderx.com> wrote:

> 1) output messaging that enables a user to more closely track what object
> could be causing the problem (not sure about this one). I would think an
> image versus a table with keeps or a block with keeps could be flagged ...
> not sure.

I'm processing a 300 page document and currently seeing

 [echo] Generate the pdf - /files/book/book.original/pdf/xslfo.pdf
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover
     [java] [error] no space for an element, trying to recover

I'm finding it rather hard, and guesswork based,
to go through each page and guess what element
is causing this.

Some sort of hint as to the source
would be very much appreciated.

for my input, candidates also include
elements for which I have set white-space retain,
e.g. program listings?

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
!DSPAM:87,4d7629cf63731966256013!
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html