Command-line PNG export path inconsistency

[Nigel Stanger]

Inkscape 0.47pre0 and pre1, Mac OS Leopard (10.5.7) build, but possibly all platforms (currently don't have access to the resources to test this). Was definitely NOT present in the 0.46 stable release.

When exporting to PNG via the command line (--export-png), the output path appears to be relative to the input file. This is inconsistent with, for example, --export-pdf, where the input and output files are independent. This means that Inkscape may try to write the PNG to a non-existent path and thus fail.

Examples (my commentary in [brackets]):

% inkscape --file=images/foo.svg --without-gui --export-pdf=images/foo.pdf
[ This works, creating images/foo.pdf as expected. ]

% inkscape --file=images/foo.svg --without-gui --export-png=images/foo.png
[ This produces a critical error at the point of trying to write the file, output follows: ]
Background RRGGBBAA: ffffff00
Area 0:0:744.094:1052.36 exported to 744 x 1052 pixels (90 dpi)
Bitmap saved as: images/foo.png

** (inkscape-bin:34861): CRITICAL **: bool sp_png_write_rgba_striped(SPDocument*, const gchar*, long unsigned int, long unsigned int, double, double, int (*)(const guchar**, int, int, void*), void*): assertion `fp != NULL' failed
[ Inkscape then exits normally (so no crash, and hence no backtrace), but foo.png is not created. ]

% inkscape --file=images/foo.svg --without-gui --export-png=foo.png
[ This works, creating images/foo.png, but you would normally expect it to create ./foo.png. It appears to be inheriting the path from the input file, which is NOT the case with --export-pdf. Note that this latter example is an obvious workaround for the bug until it's fixed. ]

[bbyak (buliabyak)]

confirmed with last svn on linux

[Alexander Bokovoy (abbra)]

This regression in Inkscape behaviour broke generation of Samba documentation. For time being I fixed it by always using absolute paths passed to Inkscape. However, this change in the behaviour is weird and counter-intuitive and needs to be fixed.

[Alexander Bokovoy (abbra)]

Fixed in Samba git by using absolute paths when calling Inkscape. http://git.samba.org/?p=samba.git;a=commitdiff;h=217e3086c74eb0b46fab512b5887d9a5a5b7ee9a

[bbyak (buliabyak)]

fixed in 22118: now relative path is absolutized with regard to document location only if it is an export hint stored in that document; otherwise - for example if it's filename specified on the command line - it is not absolutized, which in effect means it works with regard to the current working dir from which you launch the command. Please test and let me know if this fixes it for you.