Independently encountered exactly the same when trying to do the same batch transformation, with my script like...
# eliminate all objects and text with fonts - turn into paths
find . -name '*.svg' | xargs -n1 inkscape --without-gui --verb=EditSelectAll --verb=ObjectToPath --verb=FileSave --verb=FileQuit
...and found the same issue. Works fine until I try to run it without a GUI.
Perhaps it's just impossible to actually support command line control without loading up into X (for example my command relies on font loading to turn text in to paths).
This command line control is still useful compared to pointing and clicking, but if I get this working by removing --without-gui then loading up the GUI seems to take forever for each line. The need to launch a window also means I can't use this tool headless in a server context.
Is there any decision what should be done about this important missing feature, and in the meantime are there any workarounds for the ObjectToPath scenario outlined in my command line, perhaps piping things into a --shell or manually dirtying the file somehow.
Independently encountered exactly the same when trying to do the same batch transformation, with my script like...
# eliminate all objects and text with fonts - turn into paths EditSelectAll --verb=ObjectToPath --verb=FileSave --verb=FileQuit
find . -name '*.svg' | xargs -n1 inkscape --without-gui --verb=
...and found the same issue. Works fine until I try to run it without a GUI.
Perhaps it's just impossible to actually support command line control without loading up into X (for example my command relies on font loading to turn text in to paths).
This command line control is still useful compared to pointing and clicking, but if I get this working by removing --without-gui then loading up the GUI seems to take forever for each line. The need to launch a window also means I can't use this tool headless in a server context.
Is there any decision what should be done about this important missing feature, and in the meantime are there any workarounds for the ObjectToPath scenario outlined in my command line, perhaps piping things into a --shell or manually dirtying the file somehow.