--export-plain-svg adds unnecessary transform

confirmed on Windows 10, Inkscape 0.92.1 r15371

just for the record, the value 'translate(2.5,83.5)' agrees perfectly with the coordinates of the lower left hand corner of the object relative to the lower left hand corner of the page, if you load this file into the gui and choose the ignore option.

attached is a second example, just in case this problem was somehow related to the fact that this was a legacy file from 0.91.
    the attached file was created entirely in 0.92.1 using the template file default_px.svg. Then the icon object was copied and pasted into it using a text editor, not Inkscape.
When I perform the above export command in DOS I get an offset of transform="translate(-2.5,-1106.0197)" which again agrees with the coordinates of the object in the gui. In this case the exported object is far off the page so that it is not visible in the exported file unless one zooms out a lot.

not reproduced on Inkscape 0.47pre1

Thanks! I understand, so the desired outcome is some way of exporting the icons easily without these transforms. In the original SVG there is 1 root group used as a layer with id "Layer_Icons" and then inside that is where "Icon_Sprite" "Icon_Background" and all of the other icons are. We have already wrote a script that loops through the id's of the SVG and calls the command line like this. But we would ideally want to export them with a canvas size of 18x18 that is centered and with the defs minified/vacuumed/cleaned out. One problem with this setup is that the parent group of all the icons is also exported and I believe that could be the cause of why --vacuum-defs does not work either, but even after I ungrouped them from the parent --vacuum-defs still did not work either.

This issue seems fixed in current master, i.e. Inkscape 0.92+devel (4c394ff20a, 2017-10-14).

There's still a transform of "translate(-2.5,-2.5)", but that is to be expected as Inkscape rescales the canvas to fit the (remaining) drawing by default (and needs to move the object to the upper left corner in the process).

If somebody can figure out which commit fixed it in master we can backport it to 0.92.x.

Ah sorry, forget the commit has (it's a local branch based on 5433ac0513099a4a12caba0cda8a2a9d30e13a22)

Transform issue fixed in 0.92.x in
https://gitlab.com/inkscape/inkscape/commit/a355c6b862bf24a851ee42b3ace354bd29fb7d1b

See bug #1306662 for details.

The --vacuum-defs option is working fine for me.

If you should still require a feature to export without any transform at all I suggest you create a separate feature request. However removing the remaining transform would require to modify path data which probably is not a desired results in most cases.