Bug 31537 - fo:list-block with provisional-distance-between-starts attribute (variablelist)
Summary: fo:list-block with provisional-distance-between-starts attribute (variablelist)
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: pdf (show other bugs)
Version: 0.20.5
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-05 06:29 UTC by Karl Eichwalder
Modified: 2012-04-01 07:09 UTC (History)
0 users



Attachments
works for FOP (729 bytes, text/plain)
2004-10-05 06:31 UTC, Karl Eichwalder
Details
leads to an overflow (749 bytes, text/plain)
2004-10-05 06:32 UTC, Karl Eichwalder
Details
use this stylesheet (1.74 KB, text/plain)
2004-10-05 06:33 UTC, Karl Eichwalder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Eichwalder 2004-10-05 06:29:37 UTC
FOP loops if provisional-distance-between-starts of fo:list-block elements in
nested fo:block elements is too large.  You can encounter such situation if you
use nested DocBook variable lists (variablelist) with longish term elements.

FOP reports: "[INFO] area contents overflows area in line" 

Maybe, http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26163 is related.  I'm
going to attach a test case.
Comment 1 Karl Eichwalder 2004-10-05 06:31:46 UTC
Created attachment 12936 [details]
works for FOP
Comment 2 Karl Eichwalder 2004-10-05 06:32:55 UTC
Created attachment 12937 [details]
leads to an overflow
Comment 3 Karl Eichwalder 2004-10-05 06:33:27 UTC
Created attachment 12938 [details]
use this stylesheet
Comment 4 Karl Eichwalder 2004-10-05 06:47:34 UTC
To reproduce the error run:

xsltproc --nonet -o good.fo customize-fo.xsl varlistentry-good.xml
xsltproc --nonet -o bad.fo customize-fo.xsl varlistentry-bad.xml

The difference is; good.fo (3em):
provisional-distance-between-starts="3em * 0.60+1em" 

bad.fo (23em):
provisional-distance-between-starts="23em * 0.60+1em" 

I'm told you can avoid the error using a stylesheet customization; but
nevertheless it would be nice if FOP would report a fatal error instead of the loop.
Comment 5 Pascal Sancho 2007-11-20 01:53:06 UTC
Fixed in FOP 0.94 and probably earlier versions
Comment 6 Glenn Adams 2012-04-01 07:09:21 UTC
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed