On Wed, 16 Mar 2005 10:35:38 -0500, Lou Quillio <public@...534...> wrote:

http://quillio.com/Inkscape/

Thanks, so what's wrong with it exactly? The SVG matches the PNG exactly (modulo some different fonts on my system and the missing GIF referenced from SVG).

On Wed, 16 Mar 2005 11:20:18 -0500, Lou Quillio <public@...534...> wrote:

Really? Wow. Then it must be X or Gnome on my end.

http://quillio.com/Inkscape/screenshot_eog.png

Above is what the SVG (Inkscape or plain) looks like in EOG, icon thumbnails, or if I import it into Gimp.

I don't know what is EOG, but this is obviously a problem with EOG. I tested the file in Batik and Adobe SVG plugin (which according to our FAQ are the reference renderers) and it shows the same as in Inkscape. (Except that Batik does not show the objects which are beyond the edge of the page, but that's normal.)

But if a third party confirms that the SVG looks (generally) like my first screenshot and not my second, then I guess it's time for a restart. Heck, I'll reboot. Must be some kind of weird edge case.

I'm not sure a reboot will help. My guess is that your SVG renderer misinterprets the transform= attributes on objects.

Lou Quillio wrote:

bulia byak wrote:

...

I don't know what is EOG, but this is obviously a problem with EOG.

EOG = Eye of Gnome. Image viewer, like IrfanView on Win.

But it's not just EOG, it's system-wide on Gnome 2.8/Debian, and it was sudden. At first there was no visual difference between what these various apps would render and what appeared in the Inkscape GUI. Then something happened.

I think both EOG and GIMP use librsvg for rendering SVGs, which would explain why they are both rendering it wrongly. I've also had trouble viewing SVGs in them, but I'm sure it's a problem with the library rather than your SVGs.

It's unlikely to make a difference, but you might also want to consider upgrading to the latest version of Inkscape (0.41).

On Wed, Mar 16, 2005 at 12:32:10PM -0500, Lou Quillio wrote:

Jonathan Leighton wrote:

...

I think both EOG and GIMP use librsvg for rendering SVGs, which would explain why they are both rendering it wrongly. I've also had trouble viewing SVGs in them, but I'm sure it's a problem with the library rather than your SVGs.

Yes, I think that's right. At some point I manipulated the SVG (with Inkscape) and librsvg2-2 went haywire. It rendered it properly ... up to a point. Restarting X made no difference (obviously), but nothing interfered with Inkscape .40's ability to re-open the file. Just couldn't be sure.

If you can definitely ascertain that it's librsvg, could you do a favor and send them a bug report?

Given how many things are starting to depend so much on librsvg, I think it's important to raise awareness of any incompatibilities that folks find.

Also, it would be interesting to test this in the Cairo renderer and see if it works better. If so, a possible avenue for the current librsvg using applications could be to switch to using Cairo.

As you've noticed, getting SVG supported equally across open source apps is vital. If it renders differently in different software, it defeats the purpose of having a standard. ;-)

Bryce

On Wed, Mar 16, 2005 at 02:47:01PM -0500, mental@...32... wrote:

Quoting Bryce Harrington <bryce@...69...>:

...

Also, it would be interesting to test this in the Cairo renderer and see if it works better. If so, a possible avenue for the current librsvg using applications could be to switch to using Cairo.

Cairo is not an SVG renderer by itself. IIRC, the Cairo SVG demos use a Cairo port of an old version of librsvg.

Hmm... can you give more details on this? I understood that there was the base Cairo lib, plus layered on top was an SVG rendering interface. There's a program called 'svg2png' which uses these libs to provide rendering. I did not notice rsvg included in the mix, but did I miss something?

Bryce

Bryce Harrington wrote:

If you can definitely ascertain that it's librsvg, could you do a favor and send them a bug report?

I would, but I think it's known.

http://gnomedesktop.org/node/2139

Seems like the only SVG renderers on my Ubuntu Debian install are librsvg and Inkscape's (libarot?). That means a *lot* of folks are in this boat. I just hadn't encountered it before. Placed myself in a position where I was relying on Inkscape/SVG, saw strange behavior, didn't want to take a chance.

Gnome will catch up (Cairo-wise or otherwise). As long as folks know not to trust how current GTK renders SVG, it's cool for now.

LQ

Quoting Lou Quillio <public@...534...>:

Really? Wow. Then it must be X or Gnome on my end.

http://quillio.com/Inkscape/screenshot_eog.png

Above is what the SVG (Inkscape or plain) looks like in EOG, icon thumbnails, or if I import it into Gimp. Everything that can render an SVG on my system thinks it looks like the above -- except Inkscape.

All of those (except Inkscape) use librsvg to do their SVG rendering, but librsvg's rendering is currently fairly buggy.

Without having looked at the images in question yet, I suppose it's possible (but unlikely) that Inkscape's rendering is wrong, so I'd suggest comparing renderings with e.g. Batik or the Adobe viewer, which both have better SVG support than even Inkscape.

There are some things we could do to work around the bugs in librsvg, but they would make Inkscape slower... and frankly, given how widely librsvg is used, I'd much rather the librsvg maintainers were pressured to fix the bugs.

-mental