> But since you need to set envs in a launcher in order to
> launch Inkscape correctly, I guess the behavior is quite different.
No, you misunderstood. I _am_ using the "standard" command line version of Inkscape: it is configured, compiled and installed exactly like on linux (eg with ./configure --prefix="`pwd`/inst" && make && make install), and the translations for the error messages ot the python scripts still fail. As mentioned, I have not yet tested the osx-packaged version yet, but - based on my understanding and the simulated test, it will work with the packaged version if 'inkex.py' has a test for platform 'darwin'.
My issue is with normal builds on OS X, where none of the proposed patches works to translate those error messages.
> But since you need to set envs in a launcher in order to
> launch Inkscape correctly, I guess the behavior is quite different.
No, you misunderstood. I _am_ using the "standard" command line version of Inkscape: it is configured, compiled and installed exactly like on linux (eg with ./configure --prefix= "`pwd`/ inst" && make && make install), and the translations for the error messages ot the python scripts still fail. As mentioned, I have not yet tested the osx-packaged version yet, but - based on my understanding and the simulated test, it will work with the packaged version if 'inkex.py' has a test for platform 'darwin'.
My issue is with normal builds on OS X, where none of the proposed patches works to translate those error messages.