Scour messes up paths
Bug #611296 reported by
Victor Engmark
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Medium
|
Unassigned | ||
Scour |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I tried saving the following file as optimized SVG in Inkscape, but it messes up some of the paths: http://
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Assumed information:
Options: Default
Renderer: Eye of GNOME or some such
Scour version: The one with Inkscape
Inkscape version: Unknown
--------
As for this bug, I could reproduce it with the following:
./scour.py -i verso.svg -o verso.opt.svg
Scour version: 0.25 (command-line)
Renderer: Eye of GNOME
Adding --renderer- workaround (new in 0.25) works around the bug in Eye of GNOME. (Firefox displays both files just fine, though.) Strictly speaking, this bug is in "librsvg", a library that handles SVG display for Eye of GNOME and some more applications. (See bug 370061.) It has been worked around in the latest version of Scour, so it's now invalid here; Inkscape might have yet to add the changes, though.
What version of Inkscape do you have? Could you see if there's an option called "Work around renderer bugs" in the save options for Optimized SVG?
Thanks!