On 1/15/13 5:11 AM, ~suv wrote:
Note: UniConvertor is an _optional_ dependency, not a required one, and has never been included in the package for Mac OS X [1]. Since it is used as python module in the extensions, Inkscape cannot check for its presence, and still loads the input/output extensions even if they fail to work. I don't really understand the relevancy of UniConvertor 1.1.5 here unless related to bug #1046068 https://bugs.launchpad.net/inkscape/+bug/1046068 which erroneously may trigger UniConvertor-based output extensions (or any other random output extension) on exit (expected behavior would be to simply quit silently, or to save and quit, without triggering additional output extensions). If on the other hand you ported UniConvertor 1.1.5 to OS X, and manage to include a fixed and functional UniConvertor python module in Inkscape.app, this would certainly be a great bonus feature for Inkscape on OS X (though by itself this is no fix for bug #1046068). ----- [1] UniConvertor was not ported to Mac OS X by the sk1 team, and development & maintenance of UniConvertor 1.x has stopped upstream. Even if one manages to install UniConvertor 1.1.5 on OS X, the package is only partially functional (IIRC from the time I tried (on 10.5.8), the internal font path for example is simply set to '/' which even on a modestly sized hard drive caused a time out / failure of any conversion if font names had been involved).
The Mac 0.48.4 version hits that bug. If one does not have uniconvertor, while quitting with something in the clipboard, a number of error and warning windows pop up (one claiming you need uniconvertor). Very annoying. The shortest path to annoyance removal was fixing uniconvertor and sk1libs.
V.