Actually, our SVG implementation is almost complete, only lacking a few things. I believe that the most important and substantial thing that we still do not support are the animation tags. As Inkscape is nowadays a drawing application (not an animation app yet), then I think it is not reasonable to say that we haven't succeeded in SVG implementation yet. We have solid support for the subset of SVG features that are needed for a drawing app. And this subset is substantially large.

You can expect to see animation support in some future version, and then we'll probably see an Inkscape 1.0 later, when the standard finally gets fully implemented.

So now you've just learned that some people do it differently.

What is the purpose of your comments? Is it to state that there is something wrong in the development process of Inkscape? If so, then what would you suggest us to change?

If you think it is easy, remember that you can always help us do it faster (and better). Also, no browser currently support the full SVG spec as you can see at http://www.codedread.com/svg-support.php

The version number 0.48 does not mean 48% done. Inkscape developers have chosen a version numbering scheme based on the following simple rule: We'll release Inkscape 1.0 whenever Inkscape fully supports the SVG standard. Until then we'll keep increasing the secondary number on each new release. When I joined the development team, Inkscape 0.45 did not support SVG Fonts and SVG Filters. SVG Fonts are partially implemented now and SVG Filters are fully supported (except for some minor issues). And off course there is all the work done by all the other developers too.

I haven't read all the code in my system. But lots of people certainly have read lots of portions of it, so I can expect that somebody trying to put malicious code there would have to think twice before trying that. Sooner or later somebody will see that, so it is less likely it will be put there intentionally. And if it is there indeed, then there is big chance somebody will fix it. None of this can be asserted about proprietary software.