Comment 2 for bug 793227

Drawback of the proposed solution/workaround: it won't work with file formats which depend on an script-based extension, or more complex command line usage (e.g. involving verbs executing extensions or filter effects): the script does not fully set the required shell environment, and the inkscape process launched with this command is not able e.g. to load any extension files, or predefined filter effect from the shared resources included in the application bundle.

A better solution would be to call '/Applications/Inkscape.app/Contents/Resources/script' instead, with the drawback that files provided as command line arguments then always must be referenced with their full (absolute) path names. When used within other scripts, this isn't really a problem (it might be more cumbersome though for occasional usage on the command line).