[SVG Copy/Export Converts Stoke to Path]

The shape was originally in SVG format so it shouldn't contain anything that isn't supported by SVG, however...

 

It was the mitre join causing the problem. SVG does support different join/cap styles via stroke-linecap, stroke-linejoin and stroke-miterlimit attributes (the default is a mitre join with limit 4), so there shouldn't have been any conflicts.

 

On a broader note, if a style isn't supported by the exporter it'd expect to see a warning about it during the export process, ideally with an option to ignore the warnings or generate paths for the unsupported stuff. As it was, I had to diff the exported XML to figure out why my file size increased 70x.

 

In my use case--which is, admittedly, unusual--a stroke that isn't perfectly aligned is far more preferable to the increased file size and complexity.

[SVG Copy/Export Converts Stoke to Path]

I've just started using Designer and one thing I noticed is that strokes are being converted to separate paths during the SVG export.

 

First, this causes the exported file size to balloon dramatically. For instance, one of my 5K SVGs, when imported into Designer and exported as another SVG, expands to 280K to 350K, depending on the export settings.

 

Second, this means importing and exporting an SVG is a (very) lossy process, which makes it useless as an interchange format. This also affects copying objects as SVGs.

 

Third, since I need to manipulate the SVG shapes in my own program, the processing time also increases by several orders of magnitude.