On 04 Dec 2008, at 13:14, dahepe wrote:
<snip />
I stumbled across this bug while trying to use fop embedded in an
other
application. Thus removing log4j from the classpath is not an
option. As a
workaround I replaced the percent column width entries with
proportional-column-width(XX), which produces the same results in the
output.
I'm not 100% sure, but IIC, this error only arises if the log-level is
set to DEBUG (which is not really advisable for production systems, as
it can have a significant impact on the speed of the formatting
process). I discovered it myself while debugging a run, when the IDE
could not show the value of a variable (since it also used toString())
If that is the case, the workaround would be to switch to WARN, INFO
or ERROR.
Can you check if this solves the issue for now?
I'm not entirely certain, but it seems like the fix never made it
into 0.95. IIC, this issue should not exist in FOP Trunk anymore.
Can you verify this, or send us the related FO, so we can verify
ourselves?
Is there a release schedule for fop0.96 and will this bug be fixed
in the
next stable version??
Not really a fixed schedule, but we'd like to release again early in
2009.
This bug will definitely be fixed then, since it has been committed to
FOP Trunk (which will be the basis for the next release)
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
