Slashdot Mirror
Inkscape 0.47 Released
derrida writes "After over a year of intensive development and refactoring, Inkscape 0.47 is out. This version of the SVG-based vector graphics editor brings improved performance and tons of new features, including: timed autosave, Spiro splines, auto-smooth nodes, Eraser tool, new modes in Tweak tool, snapping options toolbar & greater snapping abilities, new live path effects (including Envelope), over 200 preset SVG filters, new Cairo-based PS and EPS export, spell checker, many new extensions, optimized SVG code options, and much more. Additionally, it would be wrong to not mention the hundreds of bug fixes. Check out the full release notes for more information about what has changed, enjoy the screenshots, or just jump right to downloading your package for Windows, Linux, or Mac OS X." We've been following the progress of Inkscape for years (2006, 2005, 2004).
Their roadmap states that the 1.0 milestone is "full SVG 1.1 support".
Extensions -> Modify Path -> Color Markers to Match Stroke Yeah, that's a crappy damn interface to something that should happen automatically, but it works.
If you think Firefox renders SVGs correctly, you aren't doing much with your SVGs.
Neither gecko (Firefox) nor Webkit have SVG rendering thats useful for more than basic shapes. They lack support for large swaths of the standard.
You're response is only valid if you use Inkscape to draw basic flowcharts and smiley faces, do anything complex, Inkscape, Firefox and Webkit are severely lacking.
They claim test suite compliance, if so than thats a major step to not sucking, but only if it actually saves standard SVGs. It traditionally hasn't. Its default format uses its own extensions, and its standard svg format lacked features for no apparent reason. Hell, the Inkscape extended SVG format just seems to give you some of the standard SVG features, but using custom extensions.
So great, Inkscape SVGs are renderable in Inkscape, and really simple ones will work in Firefox and Opera. Whoopdee-doo.
Do you accept a web browser with HTML 2.0 support now days? I don't.
Photoshop has a real SVG rendering engine built in, it will load files that Inkscape doesn't have a chance in hell of loading.
If you're argument is that Inkscape's lack of standard support is OK because its trying to embrace and extend the format and break compatibility with other software (again, not some extremely simple drawing) just so it can be 'the one to rule them all', then Inkscape can go fuck itself. I use SVG because it IS A STANDARD that IS SUPPORTED PROPERLY by at least SOME software. I'm not complaining about not supporting the ENTIRE standard, no one does. What it does support and how it saves on the other hand, I expect to be proper.
Again, if you think Word HTML is acceptable, you and I have completely definitions of standard. I like my 'standard' files to actually follow the definition of the standard, not someone elses own variation.
I find it amusing that your arguing that Inkscape breaking standards is acceptable because MS did it. Two wrongs don't make a right.
Why even claim the SVG file format? Just call it what it is. Why have a 'Inkscape SVG' and a 'Standard SVG' save option? Why not just call the Inkscape version the Inkscape file format and stop trying to piggy back on the SVG standard. Why introduce confusion to others?
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
None actually - Extensions/Modify Path/Color Markers to Match Stroke. Happy now?
Do as you would be done to.