On 16.09.2008, 13:35 David wrote:
2008/9/15 Nikola Smolenski smolensk@eunet.yu:
Brion Vibber wrote:
http://codewideopen.blogspot.com/2008/09/inkscape-shell-patch.html (You'll find lots of examples of not-rendering-right files on our bugzilla -- search for SVG!)
See also http://commons.wikimedia.org/wiki/Category:Pictures_showing_a_librsvg_bug
Interesting! See also my ad-hoc benchmarks at:
http://www.mediawiki.org/wiki/SVG_benchmarks
From those I disrecommended Inkscape on Unix systems - the rendering is good, but rsvg is twice as fast and uses much less memory. (On Windows, the fact that Inkscape comes in a standalone package makes it much easier to set up and use, and mediawiki-l has many happy users of Inkscape for SVGs on Windows.)
But rsvg is a library and Inkscape is a full application, so that would *plausibly* explain the overhead (I don't know if it's actually the case).
Obviously those will need rerunning with the Inkscape shell if anyone has a spare moment :-)
What's the quality of in-browser SVG rendering on Firefox 3.0 and 3.1? Looking at it casually, FF 3 betas did good rendering but weren't very fast. OTOH, sending the hard work to the client when you know it's up to the task is reasonable these days. I believe ordinary HTML <img src="something.svg" height=nn width=nn> works fine. (Haven't tried Safari, Chrome or Opera.)
- d.
[cc: to mediawiki-l]
http://en.wikipedia.org/wiki/Image:Flag_of_Mexico.svg is 500kb, while most uses of it are 25px thumbnails. Something must be done about it. Also, there are people who still use IE5, Netscape or other kinds of nonsense who will be unable to see SVGs.