command-line usage (--export-pdf) fails with absolute paths in cygwin notation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Confirmed
|
Low
|
Unassigned |
Bug Description
Console (command-line) use of inkscape.exe to export pdf/ps/etc fails with an absolute path on Win32 . This happens with SVG files from at least Visio and Dia. (I haven't checked other input formats of flavors of svg.)
I use Cygwin on XP, and I discovered this when using dblatex for converting DocBook5 XML to PDF (when dblatex sees an SVG file referenced in XML it calls inkscape using absolute paths).
My Cygwin environment is very complete and robust -- I do a lot of development, compiling, etc.
When I test inkscape alone it clearly succeeds on relative paths but fails on absolute paths.
(Note that if you want to try this yourself then you have to patch imagedata.py because it calls inkscape with in/out files mixed up -- see: http://
I've tried your official/stable win32 installer v0.48, earlier v0.46, and nightly build 0.48+devel r10061 (Feb 21 2011). I also tried setting pythonpath, and other variables, and have made sure my shell knows which inkscape/python combo to use.
OSX version produces another error when I attempt the same test -- not sure if it's supposed to have a console mode. I didn't see a Linux binary, and since I don't have the time to compile it...
BTW, although I tried compiling the latest on win32, some of Cygwin's packages are a bit behind and well, ain't gonna happen:
configure: error: Package requirements (gdkmm-2.4 glibmm-2.4 giomm-2.4 gtkmm-2.4 >= 2.10.0 gtk+-2.0 libxml-2.0 >= 2.6.11 libxslt >= 1.0.15 cairo sigc++-2.0 >= 2.0.12 gthread-2.0 >= 2.0 libpng >= 1.2 gsl) were not met:
No package 'gdkmm-2.4' found
No package 'glibmm-2.4' found
No package 'giomm-2.4' found
No package 'gtkmm-2.4' found
So I won't be able to patch source and recompile, I just can't go down that road, but I'll be glad to test new versions.
Thanks for any help.
PS, I have far too many accounts on systems around the Net, and I prefer to subscribe/
/cygdrive/c/temp
$ inkscape -z -D --export-
$ ls -l fig0.pdf
-rwx------+ 1 jazing None 18858 Feb 25 12:50 fig0.pdf
$ rm fig0.pdf
$ inkscape -z -D --export-
** (inkscape.
** (inkscape.
** (inkscape.
tags: | added: cli win32 |
summary: |
- console export-pdf etc absolute paths not working + command-line usage (--export-pdf) fails with absolute paths in cygwin + notation |
Quoting from <http:// article. gmane.org/ gmane.comp. graphics. inkscape. user/7728>:
«Now that I got everything sorted out (thanks to all who replied!), I
figure I might as well post to the list how I automated Inkscape SVG
exporting under Windows+cygwin, perhaps it will save someone else some
time in the future. (…)
The first stumbling block was that inkscape requires full paths to the
original file and the destination file. The second stumbling block
was how to translate them for inkscape, which does not like cygwin's
/cygdrive/c/... notation.»
AFAIU full paths are no longer required with Inkscape 0.48 (at least when using formats supported by internal extensions; for script-based extensions possibly the regression reported in bug #695120 also applies to Windows builds).
Inkscape 0.48 has seen several changes with regard to the command line usage on Windows: wiki.inkscape. org/wiki/ index.php/ Release_ notes/0. 48#Command_ line_interface>
<http://