save as jessyInk bug

Please add information about OS/platform and Inkscape version to the bug description, thank you.

Which version of Inkscape did you have installed before?

confirmed on Windows 10, Inkscape 0.92.0 r15299

Not reproduced with Inkscape 0.48.5 r10040, 0.91 r13725, 0.92.0 r15299, 0.92.1 r15371 on OS X 10.7.5.

I use windows 7
previous version is 0,92

In 0,92 it worked
I cant see the revision because installing 0,93 it removed 0,92

in my case, on Windows, I had to add the command inkex.localize()
as in the attached file

Not reproduced with Inkscape 0.92.0 r15299, 0.92.1 r15371, 0.92+devel r15519 on Ubuntu 14.04.5 LTS.

Sorry previous version was 0,91 must have a brain fart...

now i use Inkscape 0.92.0 r15299

On Windows 10:
- not reproduced with Inkscape 0.91 r13725 (64bit, 7z)
- reproduced with Inkscape 0.92.0 r15299 (64bit, 7z)
- reproduced with Inkscape 0.92.1pre1 r15355 (64bit, 7z)

On Windows 10:
- reproduced with Inkscape 0.92.0 r15299 (32bit, 7z)

Seems that the export script needs to fix the detection of the inkscape executable (without relying on absolute paths on any platform, this is not necessary).

Two issues:
1) localize() has not yet been run when the effect class is initialized
This also can be reproduced if the export script is modified e.g. to prompt that the inkscape executable was found (on Ubuntu, or OS X).
2) Apparently, with Inkscape >= 0.92 on Windows, the check for the inkscape binary in findInkscapeCommand() fails always (returns None). This ought to be fixed to support executing inkscape as external process like in other extensions (restack.py for example).

Attaching possible minimal fix for both issues. The hard-coded absolute paths which are checked should be removed, but that might affect other jessyInk modules as well, and should be done separately.

The error message returned from the spawned inkscape process on Windows 10 was:

'"inkscape --without-gui --version"' is not recognized as an internal or external command, operable program or batch file.

By passing the command as string instead of as list with a string as argument for Popen(), the external process is run successfully (tested with Inkscape 0.92.0 r15299 installed from 7z into custom location on Windows 10, and on OS X 10.7.5 with a regular linux-style command line installation into custom prefix).

On Windows, the export command then still fails (either hangs or takes a really long time) when rendering the layers of the SVG file to PNG or PDF at the specified resolution, but that is likely related to bug #1659172.

More specifically bug #1655619 (which might be related to bug #1659172, though)

I'm not sure if there's a connection at all, as on my system I can always reproduce #1655619 but not #1659172.

i installed inkskape with Dutch language....

Deleting the attached diff - I am revoking my pending patches provided in this bug tracker for issues with python-based extensions distributed with Inkscape.

reproduced on Windows 10, Inkscape 0.92.2pre0 (973e216, 2017-07-25)
 using the install file inkscape-0.92.2pre0-x86.exe

Python error message is:
......................................
Traceback (most recent call last):
  File "jessyInk_export.py", line 172, in <module>
    e = MyEffect()
  File "jessyInk_export.py", line 80, in __init__
    inkex.errormsg(_("Could not find Inkscape command.\n"))
NameError: global name '_' is not defined

I have the same error in the new 0.92.3 release. I cannot save a Jessyink zip pdf or png file, in Windows 10 in my notebook. I have Debian Stretch in a desktop computer, and I have no problems. So the bug is only in Windows.
I tried to add the command inkex.localize(), as wrote by Alvin Penner and the error changes in "could not find Inkscape command"

New install of:
Windows 10 Home
Version 1709
OS build 16299.125

First time install of Inkscape 0.92.3 (2405546, 2018-03-11)

Save As [jessyink zipped pdf or png output (*zip)]
returns an error message.

screenshot attached.

attached is a slightly edited version of jessyink_export.py which works for me on Windows 10

I have installed Inkscape 0.92.4 (5da689c313, 2019-01-14) on Windows10 and get the same mesage when trying to save a JessyInk pdf/png zip

Traceback (most recent call last):
  File "jessyInk_export.py", line 172, in <module>
    e = MyEffect()
  File "jessyInk_export.py", line 80, in __init__
    inkex.errormsg(_("Could not find Inkscape command.\n"))
NameError: global name '_' is not defined

I changed the JessyInk_export.py and now I get the message

"Das JessyInk-Skript ist in dieser SVG-Datei nicht installiert oder hat eine andere Version als die JessyInk-Erweiterung. Bitte wählen Sie "install/update..." aus dem "JessyInk" Untermenü des "Erweiterungen" Menü, um das JessyInk-Skript zu installieren oder zu aktualisieren." (Org)

"The JessyInk script is not installed in this SVG file or has a different version than the JessyInk extension. Please select "install/update..." from the "JessyInk" submenu of the "Extensions" menu to install or update the JessyInk script."

When I install/update nothing changes.

I installed Inkscape portable on an external drive and the same problem occurs.

Before I only used the portable version on a different external drive and it worked very wee.