RESEND: Bug with EPS-sizing upon import...
[Please cc: me on replies]
Hi,
I'm resending this after not hearing any responses to my first email over a period of two weeks... :)
I'm using Inkscape 0.40 packaged for Debian unstable. If its an issue, I'm also using the AFPL-licensed version of ghostscript, version 8.14. I have noticed the following issue/bug, since I started using Inkscape, with version 0.39.
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. For example, if I create both an EPS file and an SVG file produced by the command line version of potrace (which I was using with inkscape before it was included in the program as of version 0.40), using the exact same options and the exact same input file, they will import into Inkscape (both 0.39 and 0.40) with different sizes. The svg imported file will accurately reproduce the size of the EPS that I see when I use that EPS with other members of my tool chain (scribus, epstopdf, xpdf, acroread, etc.). Any ideas?
Do you need anything else to quantify this? It appears very reproducible to me.
Furthermore, when I export EPS from Inkscape (both 0.39 and 0.40), they appear (at least according to the "file" utility, to be regular postscript, rather than encapsulated postscript). I've tentatively tracked this down to be the lack of the full first-line of "%!PS-Adobe-3.0 EPSF-3.0" and instead only having "%!PS-Adobe-3.0". Ghostscript utilities, such as eps2eps, produce the full line, while inkscape produces the shorter version. Changing the latter to the former seemed to convince the Linux "file" utility that the file was now EPS. Any ideas on what's the right thing to do?
Thanks again for a truly magnificent product. How it has wonderfully surpassed my expectations.
Take care, Daniel
PS I"ve given it to 6-8 of my less Linux-aware friends for use on their Windows boxen in the past few weeks. They are grateful.
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).
On Mon, 20 Dec 2004, Daniel wrote:
Furthermore, when I export EPS from Inkscape (both 0.39 and 0.40), they appear (at least according to the "file" utility, to be regular postscript, rather than encapsulated postscript). I've tentatively tracked this down to be the lack of the full first-line of "%!PS-Adobe-3.0 EPSF-3.0" and instead only having "%!PS-Adobe-3.0". Ghostscript utilities, such as eps2eps, produce the full line, while inkscape produces the shorter version. Changing the latter to the former seemed to convince the Linux "file" utility that the file was now EPS. Any ideas on what's the right thing to do?
Actually EPS places some rather detailed and stringent requirements on the organization and formatting of the postscript file, as well as mandating certain specially formatted comments describing the document layout.
The EPSF declaration is just a promise that those requirements have been observed.
If someone would like to go in and rework our postscript output to meet the EPS specification, that would be helpful. For the most part I suspect we already do, except we need the special comments.
-mental
participants (3)
-
bulia byak
-
Daniel
-
MenTaLguY