[Bug 53850] fop does not support some SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=53850 --- Comment #5 from Mathieu Malaterre mathieu.malate...@gmail.com --- (In reply to comment #3) (In reply to comment #0) Created attachment 29352 [details] Input docbook It seems fop 1.0 does not support some type of SVG. I am attaching one particular such example. Clearly the raster image embedded (bottom center) has disapear. Please be more specific than some type of SVG. If only I knew... I believe that this one is failing because the internal PNG file is actually embedded (as mime64 within the SVG). But again this is a pure guess. I am attaching the input docbook file, the input svg file and the generate fo file. In the future, please do not attach docbook files. The canonical input to FOP is an XSL-FO (FO) file, the canonical output is PDF. So do include an FO and PDF file. You have included the FO file, but not a PDF output. Done. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53850] fop does not support some SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=53850 Pascal Sancho psancho@gmail.com changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Pascal Sancho psancho@gmail.com --- I see no differences between inkscape view and produced PDF using FOP (1.0 and trunk) Tried too against IE9 and FF: same conclusion. Diving into the svg file, it is hard to figure if something is wrong or not, because of its size and its complexity. So, from what I can see, the provided test case works as expected for me. Feel free to reopen if the issue persists on your side, but please, provide simpler test case (both XSL-FO and SVG) to point easily what is wrong. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53850] fop does not support some SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=53850 --- Comment #7 from Mathieu Malaterre mathieu.malate...@gmail.com --- Created attachment 29363 -- https://issues.apache.org/bugzilla/attachment.cgi?id=29363action=edit Chromium display -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53850] fop does not support some SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=53850 --- Comment #8 from Mathieu Malaterre mathieu.malate...@gmail.com --- Created attachment 29364 -- https://issues.apache.org/bugzilla/attachment.cgi?id=29364action=edit inkscape display -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53850] fop does not support some SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=53850 Mathieu Malaterre mathieu.malate...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #9 from Mathieu Malaterre mathieu.malate...@gmail.com --- (In reply to comment #6) I see no differences between inkscape view and produced PDF using FOP (1.0 and trunk) Tried too against IE9 and FF: same conclusion. I agree FF does not display it properly. I do not have access to IE9. However I have attached output from chromium and inkscape (I used inkscape to generate this image actually). So yes definitely this SVG does not diplsay as in inkscape view. Diving into the svg file, it is hard to figure if something is wrong or not, because of its size and its complexity. So, from what I can see, the provided test case works as expected for me. Feel free to reopen if the issue persists on your side, but please, provide simpler test case (both XSL-FO and SVG) to point easily what is wrong. Let's start by re-opening this issue. And then if you could comment out what you think the error can be going from I can reduce the test case. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53850] fop does not support some SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=53850 --- Comment #10 from Mathieu Malaterre mathieu.malate...@gmail.com --- On linux one can also use to display the SVG: $ rsvg-view autosynch.svg Works fine on my side with version 2.26.3 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53850] fop does not support some SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=53850 Pascal Sancho psancho@gmail.com changed: What|Removed |Added Status|REOPENED|NEEDINFO --- Comment #11 from Pascal Sancho psancho@gmail.com --- (In reply to comment #9) I agree FF does not display it properly. I do not have access to IE9. However I have attached output from chromium and inkscape (I used inkscape to generate this image actually). So yes definitely this SVG does not diplsay as in inkscape view. I persist in seeing no differences between *all* views (yours and mine) I can get, comprising your PDF and your Chrome. Can you point exactly the difference between what you expect and what you get? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53850] fop does not support some SVG
https://issues.apache.org/bugzilla/show_bug.cgi?id=53850 Mathieu Malaterre mathieu.malate...@gmail.com changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INVALID --- Comment #12 from Mathieu Malaterre mathieu.malate...@gmail.com --- (In reply to comment #11) (In reply to comment #9) I agree FF does not display it properly. I do not have access to IE9. However I have attached output from chromium and inkscape (I used inkscape to generate this image actually). So yes definitely this SVG does not diplsay as in inkscape view. I persist in seeing no differences between *all* views (yours and mine) I can get, comprising your PDF and your Chrome. Can you point exactly the difference between what you expect and what you get? Ok I understand what is going on wrong now. Both xpdf and evince from my linux station have a broken rendering engine. Opening the file from acrobat reader works as expected. Closing. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53860] New: The pdf-transcoder jar created by fop 0.94 and later includes classes from commons and avalon
https://issues.apache.org/bugzilla/show_bug.cgi?id=53860 Priority: P2 Bug ID: 53860 Assignee: fop-dev@xmlgraphics.apache.org Summary: The pdf-transcoder jar created by fop 0.94 and later includes classes from commons and avalon Severity: blocker Classification: Unclassified OS: All Reporter: djgraff...@gmail.com Hardware: All Status: NEW Version: all Component: pdf Product: Fop The build for apache FOP produces a jar which includes partial subsets of classes from commons-io, commons-logging, and avalon. By doing this, it will potentially destabilize applications that are dependent on these libraries. Many web-application containers do not specifically enforce load order of jars and as a result if the pdf-transcoder.jar from 0.94 (and whatever it is in later releases) is loaded before the proper commons-io, commons-logging etc jar files it will cause signature errors and other runtime errors to occur. I discovered this while using the Eclipse BIRT Report Engine in a non-osgi fashion within a web application. My application logic utilizes a much newer version of commons-io. Please remove the import or merging of these class file subsets from the build process and add a dependency on the full jars in question. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53400] [PATCH] new ODT render
https://issues.apache.org/bugzilla/show_bug.cgi?id=53400 --- Comment #19 from Marek Jagielski marek.jagiel...@gmail.com --- The wiki page available at: http://wiki.apache.org/xmlgraphics-fop/ODT_render -- You are receiving this mail because: You are the assignee for the bug.
