Thanks for the excellent test case! I will investigate if no else does it.
Note: incidentally your example does not run in fop-trunk due to a
regression bug with formatting of doubles.
On 5/28/12 3:04 AM, Jan Hilberath wrote:
I found that depending on the value of the "overflow" attribute, the
stroke of "path" elements may be rendered wrong.
Having defined multiple paths, setting one of them to be dashed with
"stroke-dasharray" causes subsequent paths to be dashed too, if the
overflow attribute is set to "auto" or "visible".
It seems to only happen when using the InputHandler.renderTo() method.
I tried the following ways to render the SVG:
Draws the paths incorrectly, i.e. subsequent paths have dashed stroke
when "auto" or "visible" is used.
3) Batik Squiggle
A sample maven project that demonstrates the issue is available here:
I would appreciate if someone could have a look at this.