Well, I reported the bug about having to resave gradients to render correctly with librsvg: http://bugzilla.gnome.org/show_bug.cgi?id=161467
But they make a good point about reordering gradients:
------- Additional Comment #5 From Dom Lachowicz 2005-01-02 16:32 ------- it is best, in my opinion, if the SVGs are emitted in a "streamable" format, which means that gradient 578 should appear before gradient 581 in the file.
technically librsvg, not inkscape, is at fault here. but that doesn't mean that inkscape still isn't doing something stupid.
Is there any way that Inkscape can reorder gradients according to number?
Thanks, Andrew
On Tue, 4 Jan 2005, Andrew Conkling wrote:
Well, I reported the bug about having to resave gradients to render correctly with librsvg: http://bugzilla.gnome.org/show_bug.cgi?id=161467
*sighs* Apparently they're still convinced that librsvg is conformant to the standard (it's not). I added a comment.
[ Those following along at home are invited to read the SVG 1.1 specification themselves, in case I missed something. ]
But they make a good point about reordering gradients:
Is there any way that Inkscape can reorder gradients according to number?
The numbering is sort of arbitrary, so that approach wouldn't work consistently.
Ordering objects in <defs> according to their dependencies (what they're really asking for) would require some serious work, which I don't think is worth it for the sake of a non-compliant viewer.
If the librsvg folks want to go off and make up their own vector markup language based on SVG, fine, but we're not obligated to go out of our way to support it.
-mental
participants (2)
-
Andrew Conkling -
MenTaLguY