vonHalenbach: I don't see how the fact that the current mechanism prevents the loss of vector data is linked to this bug.
The bug (or RFE maybe) is that the typical workflow when productng pdfs is to have the svg be the document and the pdf the export target. For instance, batch export is really nice, but why restrict it to ugly pngs? Moreover, the current solution with "save a copy" is really sub-optimal: the name of the export is never remembered between sessions, and exporting only a part of the drawing is clumsy. And consistency is also really bad: everyone thinks of saving as pdf as an export, not a save. Witness the fact that if your save your work as pdf and close, inkscape nags you.
vonHalenbach: I don't see how the fact that the current mechanism prevents the loss of vector data is linked to this bug.
The bug (or RFE maybe) is that the typical workflow when productng pdfs is to have the svg be the document and the pdf the export target. For instance, batch export is really nice, but why restrict it to ugly pngs? Moreover, the current solution with "save a copy" is really sub-optimal: the name of the export is never remembered between sessions, and exporting only a part of the drawing is clumsy. And consistency is also really bad: everyone thinks of saving as pdf as an export, not a save. Witness the fact that if your save your work as pdf and close, inkscape nags you.