AFAIU the location of the locale files depends on prefix used for configure on linux/osx, and might be a relative path if packaged (osxapp). The current workaround for win32 will likely fail for the portable version and for users who didn't installed Inkscape into the default location.
Could 'PACKAGE_LOCALE_DIR' (defined via configure.ac) or 'INKSCAPE_LOCALE' be added to 'set_extensions_env()' in 'src/main.cpp' (similar to PYTHONPATH), so that the externally spawned python script 'inkex.py' does inherit an environment variable containing the path to the currently configured locale dir?
AFAIU the location of the locale files depends on prefix used for configure on linux/osx, and might be a relative path if packaged (osxapp). The current workaround for win32 will likely fail for the portable version and for users who didn't installed Inkscape into the default location.
Could 'PACKAGE_ LOCALE_ DIR' (defined via configure.ac) or 'INKSCAPE_LOCALE' be added to 'set_extensions _env()' in 'src/main.cpp' (similar to PYTHONPATH), so that the externally spawned python script 'inkex.py' does inherit an environment variable containing the path to the currently configured locale dir?