Comment 3 for bug 1617281

> Is it hard to convert the given filenames to their absolute paths in it?

Not possible (because ... the current legacy implementation of relocation support requires that the actual inkscape binary is launched from a specific path inside the application bundle, else inkscape fails to find and load required shared resources looked up at a path relative to the application bundle's top-level directory. Thus any shell script launcher is required to change directory to the top-level directory inside the application bundle first, before launching the inkscape binary itself, which of course requires that input and output files are referenced with absolute paths).

The known limitation has a long history and over time suffered additional setbacks due to changes implemented in inkscape core e.g. to improve support for other proprietary platforms (in this case: Windows).

A branch with a proposed minor refactoring of the internal relocation support for Mac OS X application bundles which would improve the current situation unfortunately never received attention or review by core inkscape developers.

Your best chances are to be patient and wait/hope for GTK3-based packages for future Inkscape releases (0.93 or later) - the switch to GTK3 (with Quartz backend) requires a more-or-less complete rewrite of Inkscape packaging for macOS from scratch anyway, and hopefully will not repeat the rather “simplistic” relocation support implemented in legacy packaging.

With regard to homewbrew casks - whatever is offered there is not maintained by the inkscape project, and the maintainers of such casks need to deal themselves with known upstream limitations in whichever way they think is appropriate (the inkscape project itself doesn't track issues with third-party package managers like e.g. homebrew casks).

Linking as duplicate to bug #181639 as mentioned earlier.