On 1/16/13 10:36 AM, ~suv wrote:
On 16/01/2013 16:56, ~suv wrote:
On 15/01/2013 18:17, Valerio Aimale wrote:
- bunch of improvements and changes in the build system
- Since you seem to be a real wizard with regard to creating osx app
packages: How difficult do you think would it be to include a minimal ghostscript installation in the application bundle, with 'gs' itself in 'Resources/bin'? As far as I know this is still a big obstacle for many Mac users who want to open / edit PostScript files in Inkscape.
Sorry, correcting an obvious mistake: the dependency for PS/EPS input is of course 'ps2pdf' not 'gs' itself...
Thanks, I've also become a gtk2 wizard to integrate inkscape into Mac OS X ... dunno if you noticed .......... :-)
There are several scripts with the name psXXpdf
ps2pdf is a script that is part of gs. You were correct, if we want to bundle ps2pdf, we would carry over gs as well.
pstopdf part of a (name your favorite) texmf distribution (I think it's a ruby script)
pstopdf, installed in Mac OSX as '/usr/bin/pstopdf' is proprietary, possible closed source, Apple software.
To make things interesting, I will thrown in the hat pstoedit. In my TeX/LateX/METAFONT/METAPOST heydays (those were good days) I figured that pstoedit was the best in converting ps/eps to editable format. Far superior to gs and ruby script. Maybe we could write an svg exporter/backend for it? the author of pstoedit (all opensource) has a shareware svg exporter
Or would /usr/bin/pstopdf be good enough?
V.