Re: [Inkscape-devel] RESEND: Bug with EPS-sizing upon import...
Hi Bulia,
Thanks for the reply...
I'm guessing that you shouldn't need skencil to reproduce this bug and do a test EPS import, since I don't have it on my system and EPS imports work (I always assumed that you'd use ghostscript for EPS imports).
Anyway, that bug looked familiar but the consensus was that something might be wrong due to an Adobe Illustrator issue. Mine however are EPS outputs produced only using Free Software tools (potrace from gimp-based input scan). If it really helps you, I could probably send you the inputs off-list, but I'd prefer to keep them private unless necessary. For the record, I can make it do this with any sample EPS file I gave it (comparing it to size in ghostview or through import into scribus).
Thanks for the help. Let me know if there's anything else I can do.
Any ideas about Postscript versus EPS recognition issue I mentioned also?
Take care, Daniel
Whenever I place EPS files into a new Inkscape document, they appear to be smaller (in pixel size or actual size, based upon bounding box) than they should be.
It seems to be this bug:
http://sourceforge.net/tracker/index.php?func=detail&aid=1027699&gro...
If you attach there your comments and the sample EPS and SVG files from potrace it would be very helpful. The bug seems to be easy to fix (apparently the px and pt units are confused somewhere, we had several bugs of this kind) but I can't fix it now because I don't have Skencil installed (afaik we can only import EPS via Skencil).
Anyway, that bug looked familiar but the consensus was that something might be wrong due to an Adobe Illustrator issue. Mine however are
EPS
outputs produced only using Free Software tools (potrace from gimp-based input scan). If it really helps you, I could probably send you the inputs off-list, but I'd prefer to keep them private unless necessary. For the record, I can make it do this with any sample EPS file I gave it (comparing it to size in ghostview or through import into scribus).
Well if you can reproduce it with any EPS sample, just upload a sample you're more comfortable with to the tracker. I understand wanting to keep the files private, so if you can reproduce it with other "sample" files that don't need to be private, just go that route. It might be fixed faster if sent to the tracker than if directly to Bulia only... not saying that will be the case, but if more devs have more information (and the time to fix it sooner), than it's at least potentially faster. Plus it helps track the process from initial reporting of the issue, all the way through the resolution more accurately.
-Josh
participants (2)
-
Daniel
-
Joshua A. Andler