before/after are different with librsvg

Bug #654759 reported by Carl Karsten on 2010-10-04
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Low
jazzynico
Scour
Undecided
Unassigned
librsvg
Fix Released
High
librsvg (Ubuntu)
Medium
Unassigned
scour (Ubuntu)
Undecided
Unassigned

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

Carl Karsten (carlfk) wrote :
Carl Karsten (carlfk) wrote :
Carl Karsten (carlfk) wrote :
Carl Karsten (carlfk) wrote :
Changed in scour:
status: New → Invalid

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

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?

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

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.

Changed in scour:
assignee: nobody → Louis Simard (louis-simard)
status: Invalid → Fix Committed
su_v (suv-lp) on 2010-10-05
summary: - before/after are different with libsvg
+ before/after are different with librsvg
tags: added: exporting extensions-plugins
jazzynico (jazzynico) on 2010-10-05
Changed in inkscape:
assignee: nobody → JazzyNico (jazzynico)
status: New → Triaged
Changed in librsvg:
importance: Unknown → High
status: Unknown → New
jazzynico (jazzynico) on 2011-02-02
Changed in inkscape:
importance: Undecided → Low
milestone: none → 0.48.2
Martin Pitt (pitti) wrote :

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

Changed in scour (Ubuntu):
status: New → Fix Released
jazzynico (jazzynico) on 2011-04-01
Changed in inkscape:
milestone: 0.48.2 → 0.49
jazzynico (jazzynico) wrote :

Fix committed in the trunk, revision 10180.

Changed in inkscape:
status: Triaged → Fix Committed

This bug is fixed in release 0.26 of Scour.

Changed in scour:
status: Fix Committed → Fix Released
Changed in librsvg (Ubuntu):
status: New → Incomplete
status: Incomplete → Triaged
importance: Undecided → Medium
Changed in librsvg:
status: New → Fix Released
Sebastien Bacher (seb128) wrote :

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

Changed in librsvg (Ubuntu):
status: Triaged → Fix Committed
jazzynico (jazzynico) on 2015-02-14
Changed in inkscape:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.