Indeed. You have found a bug. Interestingly, it looks better on the PostScript side, even if the line width seems to be off (known problem). Someone will have to get a look at the code. I can't promise that I'll have time anytime soon. Would you please file a bug report in BugZilla so this doesn't get lost? Please also attach the test files instead of copy/pasting them into the text. Thank you very much.
You'll realize that FOP 1.0dev is not quite ready for productive use, even though I would've hoped the SVG part is less buggy than it seems. On 05.05.2004 22:42:47 Krautbauer, Bruce wrote: > I'm pretty sure this is a bug, but I guess there might be something > special about how svg markers are handled when rendering to PDF so I > thought I should run it by here first. > > I have an SVG file that renders properly when viewed with the Adobe 3.0 > viewer, with batik 1.5.1 squiggle and if included as an external-graphic > it generates properly using fop.0.20.5. If I run the same .fo and .svg > through fop 1.0dev I see two sets of problems. First, if there is a > positive SVG translation being applied and stroke-opacity is 0 the > marker position is off. Second, if the translation is negative then > both the line and marker positions are incorrect and if in addition > stroke-opacity is 0 then the markers are not displayed at all. I know > it sounds a little weird. The best thing is to run it and look at it. > (code included below) > > Is there, by chance, something special I need to do with my .svg or .fo > to get this to work properly with fop 1.0dev? Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
