Summary: Incorrect table-unit computation if proportional-column-
width() is used as a subexpression
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Originally posted on fop-users@ by Lou Masters (29-02-2008):
In 0.20.3, I used to do the following to give one of my columns some extra size
and ensure it always had a minimum:
In 0.94, this now produces bizarre results. I got around it by changing the
width to something like:
This seems to be OK. My question is this: Should my original method have ever
worked? Was it correct?
The initial reply was that expressions like these are perfectly legitimate
according to the XSL-FO Recommendation.
In the meantime, I re-checked the behavior of this expression in FOP Trunk, and
it seems to be completely non-functional.
The reason is that an expression like the above is parsed into a
As a result, the loop in
org.apache.fop.layoutmgr.ColumnSetup.computeTableUnit() does not detect the
TableColLength, and in the attached sample, returns a double value of 0.0 for
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.