Comment 18 for bug 498814

For the eps file:

- The Python shell does open.
- It doesn't make it to any import settings. Instead, an error message appears saying "Inkscape encountered an internal error and will close now." I hit OK, then the Windows error reporting dialog appears.
- No output other than what you indicate is shows up on the console.

For the epstopdf-converted pdf:

- The Python shell does *not* open.
- Instead, the dialog with the error ""Inkscape encountered an internal error and will close now" displays almost immediately, after which the Windows error reporting dialog appears.
- Nothing makes it to the console before it closes, not even the message about finding an appropriate interpreter. However, opening the inkscapec-generated PDF also does not display this message, so my guess is that pdf is handled more natively by Inkscape components, whereas the eps requires some Python glue to help Inkscape out.
- At any rate, the import settings dialog doesn't appear before Inkscape crashes.

To add to the confusion: when upgrading to gnuplot 4.4.0, I'd forgotten that I now can generate PDF straight from gnuplot. This can be done with the PDF terminal, which uses Ghostscript I'd guess, or the pdfcairo terminal, which uses cairo. Both of these open in Inkscape.

If any of you are familiar with gnuplot, below are the plot commands I used to set up the output and generate the plot.

set xrange [0:2*pi]
set samples 1000
set term postscript eps enhanced solid color
set output "test.eps"
plot sin(x)
set term pdfcairo enhanced solid color
set output "test-gpdfcairo.pdf"
plot sin(x)
set term pdf enhanced solid color
set output "test-gpdf.pdf"
plot sin(x)