before/after are different with librsvg

[Carl Karsten]

I don't know if this is a problem with scour or librsvg, but I don't know where to file a bug against libsvg, so you win!

I did this:

$ wget http://tavmjong.free.fr/INKSCAPE/MANUAL/images/SVG_TESTS/svg_test.svg
$ inkscape svg_test.svg

selecte the pattern, (its the small pattern labelled "Pattern")
Edit/Copy
File/New/A4
Edit/Paste
Make it big so you can see the detail:
using the x/Y and H/W entry fields in the controls bar of the select tool
set the x,y to 0,0 and hight/width to 400,400 mm
(box should about fill the page)

File/SaveAs pattern1.svg
./scour.py <../pattern1.svg >../pattern1a.svg

$ convert pattern1.svg pattern1.png
$ convert pattern1a.svg pattern1a.png

[Louis Simard (louis-simard-deactivatedaccount)]

As you correctly pointed out, this bug exists in librsvg. librsvg is a GNOME project, so bugs for that library are tracked on the GNOME Bugzilla.

Please see this bug report and comment on it if desired: https://bugzilla.gnome.org/show_bug.cgi?id=620923

In the meanwhile, the bug has been worked around in Scour: Use the --renderer-workaround option when converting files with command-line Scour, or the 'Enable renderer workarounds' option if using Inkscape's Scour output (Save as -> Optimized SVG).

ex.
./scour.py -i FILE -o OUTFILE --renderer-workaround
./scour.py --renderer-workaround < FILE > FOUTILE

[Louis Simard (louis-simard-deactivatedaccount)]

Perhaps the renderer workarounds should be enabled by default and disabled on demand, instead of disabled by default and enabled on demand, due to cases like this one. Opinions?

[Carl Karsten (carlfk)]

I just discovered that scour is built into inkscape, and its defaults
do not expose this problem and I don't do enough work like this to
have an opinion.

but because you asked... make the workaround the default until
librsvg is fixed.

On Mon, Oct 4, 2010 at 4:47 PM, Louis Simard <email address hidden> wrote:
> Perhaps the renderer workarounds should be enabled by default and
> disabled on demand, instead of disabled by default and enabled on
> demand, due to cases like this one. Opinions?
>
> --
> before/after are different with libsvg
> https://bugs.launchpad.net/bugs/654759
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in libRSVG - SVG Rendering Library: Unknown
> Status in Scour - Cleaning SVG Files: Invalid
>
> Bug description:
> I don't know if this is a problem with scour or librsvg, but I don't know where to file a bug against libsvg, so you win!
>
> I did this:
>
> $ wget http://tavmjong.free.fr/INKSCAPE/MANUAL/images/SVG_TESTS/svg_test.svg
> $ inkscape svg_test.svg
>
> selecte the pattern,  (its the small pattern labelled "Pattern")
> Edit/Copy
> File/New/A4
> Edit/Paste
> Make it big so you can see the detail:
> using the x/Y and H/W entry fields in the controls bar of the select tool
> set the x,y to 0,0 and hight/width to 400,400 mm
> (box should about fill the page)
>
> File/SaveAs pattern1.svg
> ./scour.py <../pattern1.svg >../pattern1a.svg
>
> $ convert pattern1.svg pattern1.png
> $ convert pattern1a.svg pattern1a.png
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/librsvg/+bug/654759/+subscribe
>

--
Carl K

[Louis Simard (louis-simard-deactivatedaccount)]

Enabled renderer workarounds by default in Scour r194.

Opening an Inkscape task to track the status of this bug in Inkscape's bundled version of Scour.

[Martin Pitt (pitti)]

We have that fix in the current Ubuntu package, closing package task.

[jazzynico (jazzynico)]

Fix committed in the trunk, revision 10180.

[Louis Simard (louis-simard-deactivatedaccount)]

This bug is fixed in release 0.26 of Scour.

[Sebastien Bacher (seb128)]

The issue has been fixed upstream in https://git.gnome.org/browse/librsvg/commit/?id=5ba4343bccc7e1765f38f87490b3d6a3a500fde1
The fix should be in Ubuntu with the new version update