Bob Jamison wrote:
1) Use the one specified in the prefs, (defaults to none)....
2) Use the location of inkscape.exe to hardcode the interpreter's
relative to it. If it doesn't exist.....
3) Search the PATH (what is currently happening).
This will still allow the end user to specify which python.exe he
if he is designing a new Effect.
I committed code to test in this order.
Interpreters we package with
Inkscape should be called python/python.exe, perl/perl.exe, ruby/ruby.exe,
This seems to work ok on Win32. Can people please test this on Linux,
to make sure that I didn't break anything? I rewrote some code away
to Glib::ustring, to better handle Unicode.