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

Michael Sulyaev msulyaev at renderx.com
Fri Feb 11 16:11:21 PST 2011


On 02/05/2011 05:52 PM, Dave Pawson wrote:
> [error] no space for an element, trying to recover
> [277][278][279]
>
> Not a very helpful error IMHO?
> Is there any way I can trace it to some source please?
>
> Are the numbers page numbers in the output?

Hello Dave,

The numbers in the log are the page numbers. The error message is not 
very helpful, indeed, but at least it says [error], and effectively 
points to page 277, which must be missing something from the source FO.

Tracing down to a particular FO element that did not fit and was dropped 
does not usually take too long. Matching from PDF back to FO on text 
that begins and ends xsl-region-body on that page gives you the first 
estimate of the boundaries. Then search for large things like Images or 
containers with explicitly set dimensions, or even tables with rotated 
cells.

If you cannot find it, please send me the source FO.

The real problem with this situation is that the correct behavior would 
be to report the error and stop processing, and not to try to recover at 
all, because at this moment it is already clear that the rendered result 
does not fully represent to the input source.

Regards,
Michael Sulyaev
RenderX


More information about the Xep-support mailing list