![](https://secure.gravatar.com/avatar/0ccd1d24c5fb7569432c666a347ae5da.jpg?s=120&d=mm&r=g)
On Mon, 2005-03-28 at 12:08 -0600, Craig Gotthardt wrote:
I tried to get the EPS ext to not fail. I edited (with notepad) the eps_input.inx file and put in "my path" to ghost script in place of the "path" but Inkscape complained and would not start. I put the file back to how it was originally but Inkscape still complained. When I put the backup copy of the file I had made, back into folder Inkscape started again. Is there a certain format the .inx must be saved as, like UTF-8 or something? OR does it check the file dates? I added my ghost script path to "Environment Variables" hoping this would make it find it. Still got error on EPS Input ext. I wonder if it has to do with gs actually being gswin32.exe?
All the extensions I can use are exe(windows) type, not compiled by me.
"path" just means to look in the path. Probably what you want to do is change the dependency to read "c:\blah\blah.exe" instead of putting in the XML. Any other Windows users here have Ghostscript using? I'm not sure how things work on Windows.
I tried briefly to monkey with that inx file too, on my Windows box. Do we need to do anything tricky to escape backslashes or anything? Also do you have a URL handy that breaks down what the various tags are in an inx file?
Alan