The reason for doing this is as follows. If I monitor the environment variables from inside c in the routine main.cpp, I find that the LANG variable is not set (if Inkscape was started from DOS).
If I monitor the environment variables from inside Python as called by Inkscape, I find that LANG is set.
If I monitor again in Inkscape c code called by Python called by Inkscape, it is still set.
As soon as I unset it, the crash disappears. This appears to be the difference between running from DOS versus spawning from Python.
sorry, that should read comment 33, not 6: /bugs.launchpad .net/inkscape/ +bug/1662531/ comments/ 33
https:/
The reason for doing this is as follows. If I monitor the environment variables from inside c in the routine main.cpp, I find that the LANG variable is not set (if Inkscape was started from DOS).
If I monitor the environment variables from inside Python as called by Inkscape, I find that LANG is set.
If I monitor again in Inkscape c code called by Python called by Inkscape, it is still set.
As soon as I unset it, the crash disappears. This appears to be the difference between running from DOS versus spawning from Python.