"It also imports several formats like EPS" - howto on Windows?
Is the EPS import functionality available in the Windows build? I couldn't get .39 or .41 to open .eps files.
Also, are there plans to add embedded tiff previews to exported eps? I can add them after the fact with gsview, but it's a slow manual process. (I'm interested in eps because RagTime Solo can't currently handle svg natively)
Alan
On Sun, 2005-03-27 at 11:08 -0500, R. Alan Monroe wrote:
Is the EPS import functionality available in the Windows build? I couldn't get .39 or .41 to open .eps files.
Also, are there plans to add embedded tiff previews to exported eps? I can add them after the fact with gsview, but it's a slow manual process. (I'm interested in eps because RagTime Solo can't currently handle svg natively)
To all: I'm writing this as an FAQ item, if people could give feedback -- I'll then put it in the FAQ. It is becoming a frequently asked question.
How do I get additional input formats to work in Inkscape (EPS, Sketch, others)?
Inkscape supports a variety of input formats using external tools, where it runs the program for you and puts the output into the Inkscape window. We call these Inkscape Scripts. In order for Inkscape to use these external programs they must be installed on your computer and in a place that Inkscape can find them. In order to get a list of which utilities Inkscape can't find look at the file extension-errors.log which is in Inkscape's preferences directory ($HOME/.inkscape/ on Unix clones).
As an example, here is an error possible in the extension-errors.log file:
Extension "Windows Metafile Input" failed to load because a dependency was not met. Dependency:: type: executable location: path string: wmf2svg
This error describes an error with the loading of WMF files. It says that Inkscape was looking for an "executable" (or program) in your computer's path, and the name of that executable is "wmf2svg".
Another common error is that one extension is dependent on another, so without that one working properly, the current one fails. An error of that type looks like this:
Extension "Postscript Input" failed to load because a dependency was not met. Dependency:: type: extension location: path string: org.inkscape.input.sk
Sometimes finding the individual dependencies can be difficult, this is an area of improvement in Inkscape. You can expect future versions of Inkscape to be more helpful in dealing with finding these external dependencies.
I can't vouch for the content, but I reworded some parts that sounded awkward to me. Two questions:
1) Are they really called Inkscape Scripts? In most cases, aren't they actually programs created by other people - making them neither Scripts, nor Inkscape?
2) I have never tried Inkscape on Windows, and I don't see any mention of Windows specific issues here. Would it be appropriate to include them?
Slightly Modified Version:
How do I get additional input formats (EPS, Sketch ...) to work in Inkscape ?
Inkscape supports a variety of input formats using external conversion programs, called Inkscape Scripts. In order for Inkscape to use these external programs, they must be installed on your computer, and in a place where Inkscape can find them. Every time you start Inkscape, it generates a file extension-errors.log (located in $HOME/.inkscape/ on Unix clones) that describes the program it was not able to find. If a program is listed in this file, you will not be able to make that conversion.
As an example, here is an error in the extension-errors.log file:
Extension "Windows Metafile Input" failed to load because a dependency was not met. Dependency:: type: executable location: path string: wmf2svg
This message describes an error with the loading of WMF files. It says that Inkscape was looking for an "executable" (or program) in your computer's path, and the name of that executable is "wmf2svg".
Another common error is that one extension is dependent on another, so without that one working properly, the current one fails. An error of that type looks like this:
Extension "Postscript Input" failed to load because a dependency was not met. Dependency:: type: extension location: path string: org.inkscape.input.sk
Sometimes finding the individual dependencies can be difficult. Work is currently being done to improve this area in Inkscape. You can expect future versions to be more helpful in finding these external dependencies.
On Sun, 27 Mar 2005 12:54:00 -0500, Richard Kowalczyk <richk@...489...> wrote:
- I have never tried Inkscape on Windows, and I don't see any mention
of Windows specific issues here. Would it be appropriate to include them?
I'm more than sure it would. PS/EPS import is important for many people, and if we cannot make it work on Windows, we must be very upfront about it.
Of course still better would be to make it work on Windows :)
On Sun, 2005-03-27 at 12:54 -0500, Richard Kowalczyk wrote:
- Are they really called Inkscape Scripts? In most cases, aren't they
actually programs created by other people - making them neither Scripts, nor Inkscape?
Well, they are really Inkscape Extensions implemented with Scripts. So, it is an extension to Inkscape, but the functionality happens using an external program. I've always shortened this to Inkscape Scripts, but if others have suggestions, I'm happy to hear them. (I'm not changing the name in the source code though :) )
- I have never tried Inkscape on Windows, and I don't see any mention
of Windows specific issues here. Would it be appropriate to include them?
I'm not sure there are any Windows specific errors. We had a pipe issue, but I think that is fixed now... but then again, I thought the GIMP gradient stuff worked too. Are there more issues on Windows?
Slightly Modified Version:
I like that, anyone else?
--Ted
On Sun, 2005-03-27 at 11:08 -0500, R. Alan Monroe wrote:
Is the EPS import functionality available in the Windows build? I couldn't get .39 or .41 to open .eps files.
[snip]
Inkscape supports a variety of input formats using external tools, where it runs the program for you and puts the output into the Inkscape window. We call these Inkscape Scripts. In order for Inkscape to use these external programs they must be installed on your computer and in a place that Inkscape can find them. In order to get a list of which utilities Inkscape can't find look at the file extension-errors.log which is in Inkscape's preferences directory ($HOME/.inkscape/ on Unix clones).
Aha. In my case it was:
Extension "EPS Input" failed to load because a dependency was not met. Dependency:: type: executable location: path string: gs
However, I _do_ have Ghostscript installed. Is that what "gs" refers to?
I think maybe it would be handy if the "One or more extensions failed to load" dialog box had a button to launch the error log directly, so you don't have to go digging for the log. Also, it might be useful for the dialog to have a short list of the titles of the extensions it couldn't load, a la:
* EPS Input * GIMP Gradients * Grid etc.
To me, that makes it a little more user friendly.
Alan
R. Alan Monroe wrote:
However, I _do_ have Ghostscript installed. Is that what "gs" refers to?
I think maybe it would be handy if the "One or more extensions failed to load" dialog box had a button to launch the error log directly, so you don't have to go digging for the log. Also, it might be useful for the dialog to have a short list of the titles of the extensions it couldn't load, a la:
- EPS Input
- GIMP Gradients
- Grid
etc.
To me, that makes it a little more user friendly.
Take a look over RFE 1151684 "suggestions for "Could not load extension"-dialogue" and RFE 1161172 "About|Extensions Dialog"
Work has been started on these in CVS.
participants (5)
-
bulia byak -
Jon A. Cruz -
R. Alan Monroe -
Richard Kowalczyk -
Ted Gould