On Jul 23, 2010, at 9:05 AM, Krzysztof Kosiński wrote:
W dniu 23 lipca 2010 03:06 użytkownik Jon Cruz <jon@...18...> napisał:
But don't you remember? librsvg is not a fully viable option, which is why we ended up having to include hundreds and hundreds of individually pre-rendered png files in the past attempt.
The PNG files were included because I could not add the librsvg loader to Windows devlibs. Now this is no longer a problem, so they are not strictly necessary. They could be generated on first startup or during the build.
No, you seem to have forgotten. We discussed this on the mailing list April before last, and you said you would do the PNG versions in response to the note that some icons were coming up blank for different users.
Things are ok if one sticks to requiring users to always install the latest cutting edge versions of libs on their OS, but that's not practical. Also by *design* librsvg only supports a partial subset of SVG, and as Inkscape and SVG itself both move forwards, we diverge even more.
Even old versions of librsvg can handle our icons. Furthermore, all other icons on the Gnome desktop are rendered with librsvg, so its limitations would not be unique to Inkscape.
No, this is not true. That is a source of many problems. In the past we've definitely seen core Inkscape users have librsvg not handle certain icons and result in mis-rendered or completely blank results. Just because you had seen no problems does not mean *others* are not seeing such problems. Additionally you have to keep in mind that not everyone runs a GNOME desktop or GNOME applications. KDE is actually quite a popular desktop and application framework, and KDE has *two* main SVG renderers, neither of which are librsvg.
Then we also have mentioned quite a few times that Inkscape intends to *innovate* SVG use, not follow lagging SVG adoption. Among other things we are in the process of implementing multi-res image/icon support. In discussions at SVG Open 2008 many of the W3C WG members suggested that instead of the proposed SVG <multiImage> element, that one could achieve that via CSS3 Media Queries. At SVG 2009 some of the Opera team showed implementation of such behavior.
(this article contains links and a good summary http://nimbupani.com/svg-is-coming.html )
So the bottom line there is that we should keep in mind that Inkscape is *not* like other applications. It *is* a high-quality SVG renderer, and we should not slave ourselves to the limitations of just one of the main Linux desktop environments out there. We should help Inkscape promote SVG and lead the pack, not follow the least common denominator of the more restricted use cases.