exporting to eps fails randomly(?)

Bug #1322712 reported by Tas Ras
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Confirmed
Medium
Unassigned

Bug Description

I have many different drawings in a single .svg file and I do the following to export them to .eps:
1. Select components that constitute a single drawing
2. Group them
3. File > Save a copy...
4. [Check only] Export area is drawing
5. Set the object id of the grouped object

This works most of the time without any problems and the .eps is exported successfully.

However, in some cases, an empty drawing is exported in the .eps file. The .eps file itself is not empty (checked it with text editor) and probably not corrupted (I am not familiar with the .eps format, but ghostview does not complain when opening it).
Unfortunately, I haven't noticed a definite pattern of when this problem occurs.

Still, a hint could be this: If I copy the grouped object, paste it in a fresh empty .svg file (without making ANY changes) and follow the same procedure, the .eps file is ALWAYS created successfully.

Tags: exporting eps
Revision history for this message
su_v (suv-lp) wrote :

Could you please add information about OS/platform and Inkscape version to the bug description, thx.

Any chance you could share the SVG file and an exported EPS file which renders empty, to allow further investigation and tests on other systems with different versions of Inkscape (and cairo)?

Changed in inkscape:
status: New → Incomplete
Revision history for this message
Tas Ras (rascobikoulas) wrote :

I am using Inkscape 0.48.4 r9939 (not the portable version) on Windows 7 64-bit SP1. I have seen it occuring on two different physical machines (same OS configuration).

I'd like to include the svg, but it may contain possibly copyrighted material which I'm not sure I can disseminate.
I will try to clean it up or recreate the issue and get back.
Sorry for that :/

Revision history for this message
Tas Ras (rascobikoulas) wrote :

Ok, not sure how to upload more than 1 file here, so here are 3 files:
https://www.copy.com/s/LEC3dQMyZlmP/inkscape_bug

mat.svg:
a problematic svg (I've replaced entries containing directories/file names with "XXXX.png" (or smthing))
I've grouped some components in object id g5888 and tried to export .eps, following the procedure I described above.
mat_bad.eps: the bad .eps
mat_proper.eps: the correct .eps, after exporting it from a fresh new svg (just copy-pasted object g5888 to a fresh new svg and followed same procedure)

hope that helps

Revision history for this message
su_v (suv-lp) wrote :

On OS X 10.7.5, testing export to EPS per object id (g5888):

1) only '[x] export area is drawing' checked:
- corrupt EPS file with 0.48.4 r9939, r10031 (cairo 1.12.2, 1.12.16)
- corrupt EPS file with 0.48+devel rev <= 11649 (cairo 1.12.2)

2) both export area options are checked (drawing + page):
- slightly oversized EPS file with 0.48.4 r9939, r10031 (cairo 1.12.2, 1.12.16)
- slightly oversized EPS file with 0.48+devel rev <= 11649 (cairo 1.12.2)

3) copy&paste group into new document:
- correct EPS file with only '[x] export area is drawing' checked
- slightly oversized EPS file if both export area options are checked

PDF/PS/EPS export options got changed in 0.48+devel r11654, the export area is now a radiobutton choice (bug #499965):
4) Output page size: exported object's size:
- slightly oversized EPS file with rev >= 11654 (cairo 1.12.2, 1.12.16)

Exported EPS file with current trunk r13398, cairo 1.12.16 attached.

Changed in inkscape:
status: Incomplete → New
Revision history for this message
su_v (suv-lp) wrote :

Setting status to confirmed for now - the EPS file exported with current trunk doesn't exactly match the expected size of the EPS file as generated with stable after pasting the group into a new document (-> the minimal bounding box around the content of the exported object).

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.