Alexander Roalter wrote:
On 08/17/2010 09:24 PM, Jasper van de Gronde wrote:
Alexander Roalter wrote:
... And last, how does one make a distinction (and possibly convert) a path with absolute coordinates (uppercase M at the beginning of the path) to a path with relative coordinates (lowercase m)? I think this should be as easy as changing the path's direction
Can you explain why you would need to? Currently it is treated simply as a different representation of the same path and Inkscape chooses the representation dynamically to optimize the size of the path data (which can drastically reduce file size).
It's more a matter of cleaning up the SVG. if I look through it, I see lots of things not needed in there, for unused defs to opacity,
I'm assuming you are aware of "vacuum defs"? If it fails to work, please file a bug report.
stroke-linecap, linejoin etc. declarations that only set the default value but clog up the file.
Yes, in general Inkscape needs to take those things into account more, if you have some specific examples we'd love to have a bug report for those. But realize that sometimes there is a fine line, in some cases "optimizing" our SVG may in fact be counterproductive in that it yields modest gains in file size and such but does obscure the SVG.
In addition to be able to dynamically switching between relative/absolute coordinates, there should be a possibility to clean up the svg in a way, say loose unneeded declarations, apply transformations where possible, and even lower the precision on some cases/round to some extent.
As I explained paths are currently already optimized by Inkscape (including but not limited to switching between relative/absolute), you're not going to be able to make the path data any smaller than it is right now (except by removing spaces and such, which was deliberately avoided). Is there any other reason for wanting to switch between relative and absolute coordinates?
As for the other things, a lot of that is already possible (Inkscape has two modes for applying transformations and you can set the precision at which it works). Any specific requests for enhancing the functionality are most welcome though.
I'd like to point to our bug tracker (which is also used for feature requests), if you file your request there it won't be easily forgotten: http://bugs.launchpad.net/inkscape/ We also have a section with blue prints on Launchpad that can be used for more general proposals.