On 2014-05-06 11:49 +0100, Partha Bagchi wrote:
> Yes, my builds open PDF files and I saw this Debian bug report where
> someone claimed that Inkscape uses gs instead of pstoedit:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366797

That bug report was originally filed against older versions of inkscape
(0.43-0.46). With the release of Inkscape 0.47 on 2009-11-24, PS/EPS
import was switched from pstoedit to ps2pdf (from Ghostscript):
<http://wiki.inkscape.org/wiki/index.php/Release_notes/0.47#PostScript_and_EPS_import>
<http://tavmjong.free.fr/INKSCAPE/MANUAL/html/File-Import.html>

pstoedit [1] (used in older Inkscape versions for PS/EPS import) is a
different application than ps2pdf [2] (used by current Inkscape stable
and trunk [3]). 'ps2pdf' is part of Ghostscript i.e. it is one of the
many separate command line tools installed by Ghostscript.


[1] pstoedit:
<http://www.pstoedit.net/>

[2] ps2pdf (Ghostscript):
<http://www.ghostscript.com/>
<http://www.ghostscript.com/doc/9.10/Ps2pdf.htm>

[3] (e)ps_input:
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/extensions/eps_input.inx>
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/extensions/ps_input.inx>
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/share/extensions/ps2pdf-ext.py>

> On Mon, May 5, 2014 at 10:01 PM, su_v <suv-sf@...58...> wrote:
>
>> On 2014-05-06 03:38 +0100, Partha Bagchi wrote:
>>> On Mon, May 5, 2014 at 8:40 PM, su_v <suv-sf@...58...>
>> wrote:
>>
>>>>> and I was not able to open EPS files (got a parsing error with
>>>>> "expecting "<" ...).
>>>>
>>>> Since you don't share details about how your app was created (I assume
>>>> you used custom packaging routines, too, besides your own build env for
>>>> the dependencies), I can only guess what the underlying issue might be:
>>>>
>>>> I build all gtk/glib dependencies from scratch, everything I need for
>> Gimp
>>> (you can check out my Gimp builds on my website).
>>>
>>> I downloaded your branch and built the Inkscape App using the same
>>> structure as my Gimp builds. The Inkscape App like my Gimp builds is self
>>> contained and does not rely on the User for any dylibs.
>>>
>>>> 1) Is your Inkscape.app (Inkscape-0.48-dev) able to open PDF files?
>>>> (these kind of parser errors are known from contexts where PDF
>>>> support in Inkscape is broken - e.g. because poppler was configured
>>>> without xpdf headers, or not built in at all).
>>>>
>>> See above. My builds have poppler configured with xpdf headers and
>>> associated dependencies included. My Gimp builds open PDF/EPS/PS just
>> fine.
>>> :) I'll be happy to share my Inkscape build with you (or anyone) if
>> needed.
>>
>> So your Inkscape.app build does open PDF files or not? Please note that
>> GIMP's PostScript import feature is different from Inkscape.
>>
>>>> (If poppler support was not properly compiled in,
>>>> 'org.inkscape.input.pdf' might be a logged missing dependency for input
>>>> formats like PS and EPS (see 'extension-errors.log' in the inkscape user
>>>> profile dir used by Inkscape.app - the exact location depends on whether
>>>> you used the launcher script of the 'osxmenu' branch, or your own)).
>>>>
>>>> 2) Did you verify that the bundled ps2pdf and GhostScript (I assume you
>>>> included it in the app bundle, since it is a required helper app for
>>>> PostScript input in Inkscape) works as expected?
>>>>
>>> I was going to build ps2pdf till I saw the bugreport where you said that
>>> one does not need it anymore. Gimp does not need ps2pdf to open EPS files
>>> (or Ghostscript for that matter). Just the dylib. I'll build ps2pdf and
>>> recheck this.
>>
>> Which bug report for inkscape - do you have a link? I can't imagine that
>> I said that Inkscape no longer needs ps2pdf for EPS/PS import (it still
>> does).
>>
>> In Inkscape, PS/EPS import works in two steps:
>> 1) the PostScript file is converted to a PDF file with ps2pdf from
>> Ghostscript (needs to be in $PATH).
>> 2) the just created PDF file is imported in Inkscape using built-in
>> (poppler-based) routines.
>>