Re: Getting ready for next xmlroff release

Tony Graham wrote:
> Stefan Seefeld <[email protected]> writes:
> ...
> 
>>That's great news, and I will definitely try it out. Back to the
>>
>>area split problem I was seeing: I'm not sure how to work around that,
>>as I don't know what it means, i.e. what input will trigger it.
>>Do you have any advise ? Do, by any chance, anobody here know what
>>kind of docbook construct will trigger it when using Norm's fo stylesheets ?
> 
> 
> Without having looked at the problem for a while, the code that directs that
> areas should be split should recognise that it has previously tried to split
> at the same height and failed in trying.  It should just put the unsplittable
> areas on the page and move on to the next page.
> 
> That would require keeping track of the last attempted height (and possibly
> the last FoArea that needed splitting) so it knows that it's a repeat.
> 
> Another problem that's been known to cause it, I think, is page-height="auto"
> (or no page-height specified).

I see. Noting that you mentioned a redesign of the area-generating code was
on the TODO list, may I suggest that xmlroff does not attempt any splits at all
and generate an error message instead ?
That should be a QuickHack with the benefit of

a) still generating output so people can inspect *something* and
b) be a bit more clear (to users and potential developers) about what
    missing feature caused the error.

Thanks !
		Stefan



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf