I have a SVG image which I made using Inkscape that I am trying to save as an EPS file. I was able to do this using File > Save As and saving it as an EPS. However, when I open the EPS file, part of the image does not show up. It's not cut off, but one of the paths from the Inkscape file simply fails to appear in the EPS file.




In trying to solve this myself, I tried making a new path (just a standard ellipse) to see if it was just the "2" that was the problem, and the ellipse did not show up in the EPS file either. In fact, no new paths that I created would show up in the EPS, even if the new path was a direct duplicate of one of the paths which did show up (such as the "0"). I have searched this forum and Googled the problem, but all I was able to find were instances where part of the image was cut off when saving as an EPS.

Can anyone explain why only part of my image isn't showing up in the EPS? Are there any ways to get the whole image to show up?

Are text elements converted to paths?

Can you attach a SVG for us to examine?

Yes and no; everything in the image is a path, including the words and numbers, but nothing was converted from text. All of the letters and numbers were made by hand (tracing using the pen tool), since this was made based on a preexisting image and nobody knew what the font used in it was.

I've attached an SVG, as requested.

Give this one a shot...


https://dl.dropboxusercontent.com/s/4b3 ... /20-5a.svg

If it works for you, holler back for the scoop.

That works perfectly; thank you so much! How did you get it to work?

That image requires having the clipped element (rocket body) as the highest group in the z-order. Otherwise, the clip affects any other higher element. I really don't know why, yet... I tried the same bits in other graphics with inconsistent results.

To inspect the image, I started by deleting elements to find the troublemaker. There were so many unused pieces, that it seemed faster to work from the opposite direction - copying just the visible bits to another image, one-by one, until the problem surfaced.

I suggest cleaning out the extra/unneeded elements in the image, to keep things simple and easy to deal with. While it's convenient to hide unused elements in the z-order for playing with variations (gradient fills, etc.) it can result in errors and confusion. Might be better to use incremental versions/copies and "vacuum defs" regularly.


Regards,
TD

I wasn't expecting the fix to be that simple... Again, thank you very much!