Comment 8 for bug 444194

I agree with ScislaC and suv.

> Effectively I mean this "bug" renders this format useless for further serious work (for me at least).
And in fact, in many circumstances, it does. The matter is that plain SVG doesn't support many of the edition capabilities that Inkscape offers, so this format is considered "lossy" (it loses editing parameters such as layers, and then a ton more) and should be only used for exporting or when you're positive that using it won't cause any harm.

> In other words, serious work can only really be done in the Inkscape SVG format. This doesn't strike me as a good idea.
And that's the way you've to work. Inkscape is not particular case. As gimp uses XCF, or Illustrator uses AI (or PDF with editing capabilities), or Indesign uses INDD... all native file formats, the only way to grant that all of the editing features are preserved. Now, all of the mentioned software have ways to export to PDF, JPEG, PNG, etc. but those formats can't store all the information needed for a later edition.

Personally, I see no bug. Standard (plain) SVG doesn't support many of Inkscape's features so is just technically impossible for the app to store them in that format. However, an effort to disambiguate export and save should be done in the direction gimp has taken.

Regards.