Any idea why Inkscape uses PDF 1.4 instead of a new version? I believe we're coming up on PDF 2.0 now.

Layered PDFs and other really complex drawings simply don't properly save as PDFs from Inkscape. A real hindrance.

Wouldn't it be worth saving the space in the filesize? I can't imagine it'd be that difficult to detect whether the text element has a tspan inside...

This should probably be how Inkscape acts by default, only putting in tspans if attributes are applied to chunks of the text.

I use the jQuery SVG plugin to load my SVGs, however, IE 8 and older don't work with regular SVGs.

I recently discovered http://svgboilerplate.com/ and I might trying that out for all the cross-browser goodness it promises.

What happens if you save them as optimized or plain SVG files?

Inkscape creates tspan elements inside each text element by default. Perhaps this could be cleaned up? I'm noticing that much of my XML has repetitive tspan elements that mirror their parent text element. Are these really necessary?

I'll make sure to test that. Currently I've just avoided it altogether by splitting the lines using one of the text extensions that comes with Inkscape. I also have been saving as optimized SVGs but more complex ones need to be just plain SVG (not Inkscape format) because of rendering issues.

Hey everyone, I'm brand new to the forum, I hope I can be of some use :) I've been working for several months now to find the right tools to create a next generation web2print service. My first focus is on business cards. I started out with fillable PDFs, which are garbage. Then I manually created H...