Bulia wrote:

Personally, I would much prefer to have standard system-wide high-quality SVG->PDF and PS->SVG converters that we could use, without having to code them into Inkscape. Such a modular approach would be the best for everyone. The idea that every single design app must import and export all common formats is, IMHO, a harmful misconception originated on proprietary platforms where each app has to be self-sustaining and cannot count on cooperation from other programs. We can save a lot of resources by not following this model. I see no problem in having to run Inkscape files through Scribus or some other converter [1] when I need PDF, provided it is as cross-platform as we are and produces good output.

I agree with you in principle that it might be good design to have a whole different piece of software whose job was SVG->PS or SVG->PDF. However, as far as I can tell, Scribus isn't going to fill that role, and I'm not aware of any other project that will. Scribus isn't cross-platform, it has no command-line interface AFAICT, at the moment it does not do a very good job on SVG->PDF, and I don't see any signs that they consider it to be part of their core mission to act as an automatic behind-the-scenes SVG->PDF converter that other programs can use library-fashion. To me, it would be much more logical for such functionality to be in Inkscape, rather than Scribus; but then, that's easy for me to say, since I don't have the C++ skills or the time that would be needed to do the necessary work on Inkscape :-)