Hello,

as mentioned several times in this mailing list, the eps-import in inkscape works via subsequent conversions to .ps, .sk, and finally .svg. For this purpose I tried to install all required packages on my windows machine, but for some reasons 'sketch' seems to be a little problematic (doesn't start and doesn't include 'skconvert' which is required in the last conversion step in sk2svg.sh).

Fortunately, 'pstoedit' has two ways to produce svg-output. For some reason, "-f svg" doesn't work well, but "-f plot-svg" seems to do the job. I tried this on the command line and opened the svg-file successfully in inkscape. Given that, the extension script 'eps_input.inx' could be changed to call 'pstoedit -f plot-svg' to let inkscape read in the svg-output in a more efficient way than before.

Now my problem: I didn't manage to change 'eps_input.inx' to do exactly this on my windows machine:

<inkscape-extension> <name>EPS Input</name> <id>org.inkscape.input.eps</id> <dependency type="executable">pstoedit.exe</dependency> <input> <extension>.eps</extension> <mimetype>image/x-encapsulated-postscript</mimetype> <filetypename>Encapsulated Postscript (*.eps)</filetypename> <filetypetooltip>Encapsulated Postscript</filetypetooltip> </input> <script> <command reldir="path">pstoedit.exe -f plot-svg</command> </script> </inkscape-extension>

What's wrong here? Is there anything special with windows here? I have no idea about the syntax or language at all in these extension scripts ... I'm not sure if 'pstoedit' gets executed at all. Maybe a problem with stdin, stdout, piping, etc. ?

Help is much appreciated. Thanks.

Christian.