From: Stefan S. <se...@sy...> - 2005-11-10 02:03:53
|
Tony Graham wrote: > Tony Graham <Ton...@Su...> writes: > ... > >>xmlroff 0.3.7 fulfills the letter of Stefan's request that xmlroff not go into >>an infinite loop when it can't fit something on a page. xmlroff doesn't go >>into an infinite loop anymore; it just happens to not render the problematic >>area at all. >> >>Unfortunately, I won't have much time to work on xmlroff until at least the >>middle of the month, so if there was going to be a monthly release for >>November, this was the best I can do. > > > I had some time on the train into the office (which is how I get most of the > time that I can spend on xmlroff), and both got the problematic overflowing > area to render and implemented the 'overflow' property for region-body so the > overflowing area can be clipped. > > Please try the current code in CVS to see whether it is functional enough to > be worth making another release. I get a segmentation fault after lots of 'libfo-CRITICAL' messages. The first one is (process:12015): libfo-CRITICAL **: fo_area_page_size_request:: Cannot split child:: page: FoAreaPage (0x9e8ddb8 : 2); child: FoAreaViewportReference (0x9e8dcb8 : 1) which I assume your latest work was meant to resolve. Right ? The second such message looks like an identical copy of the first, but the third one is strange again: (process:12015): libfo-CRITICAL **: Expression evaluation error: Expression not completely evaluated: '/ast.svg' Object path: /FoTree[1]/root[1]/page-sequence[5]/flow[1]/FoBlockBlock[2]/FoBlockLayout[3]/external-graphic[1] The expression in question seems to stem from an external-graphic attribute src="images/ast.svg". I thought xmlroff is able to deal with such paths. Do I remember wrongly ? The last errors, which appear to have caused the actual segfault, are assertion errors such as: (process:12015): libfo-CRITICAL **: file fo-length.c: line 320 (fo_length_get_value): assertion `length != NULL' failed Let me know if I can help debug this further. Thanks, Stefan |