eps exported not usable in Maya/CAD

Bug #1764644 reported by Thomas Kaufmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

When exporting an EPS file out of Inkscape, the result is loosing a few nodes/points after importing into target app. The same is not happening with Illustrator.

Steps to create:
build any shape and export as eps. Import into maya.

After fiddling with the files and analyzing them, it is reproducibly fixable by changing two things inside the eps:

1. the lines have to be drawn by using the lineto /l command rather than the exported curveto /c command.
2. As lines consist of two points, the redundant information for positioning have to be removed -> coordinates are saved in triples followed by the connector '/c' at the end. These have to be tuples followed by '/l'

The result is coming out inverted (upside down), but this is a rather neglectable issue.

See also the attached files.

I would boldly assume this a something that can be included into the exporter as an option and might already be inside the cairo toolset.

Inkscape Version: Inkscape 0.92.3 (2405546, 2018-03-11)

OS: Win 10

Target App: Maya, any version

Revision history for this message
Thomas Kaufmann (tkman) wrote :
Revision history for this message
Thomas Kaufmann (tkman) wrote :
Revision history for this message
Alvin Penner (apenner) wrote :

thank you for taking the time to issue a report. I have not been able to reproduce the problem using Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11), and the attached svg file.

could you attach your original svg file for testing purposes?

Revision history for this message
Thomas Kaufmann (tkman) wrote :

sorry,

forgot to attach it..

Revision history for this message
Thomas Kaufmann (tkman) wrote :

opening the EPS in Illustrator or most other applications that can view them, shows a correct result.
However, the Curve creation in Maya fails due the mentioned formatting differences.

Revision history for this message
Alvin Penner (apenner) wrote :

thank you for the file. problem not reproduced if I use the file crosslike_shape.svg.
attached is the eps file I get from Inkscape, which appears to load correctly into GSView32.exe version 4.9.

Revision history for this message
Alvin Penner (apenner) wrote :

also, as far as I can tell, the eps file is not upside dowm. could you provide details of how you perform the eps export, which export options you use?

Revision history for this message
Thomas Kaufmann (tkman) wrote :

let me emphasize the software again, I am importing it into Maya and so far only there is the incompatibility showing.
Opening your file inside maya, the same behaviour is shown.

Export is done using the saveAs command.
PostScript level 2
any text option
no rasterization
size document's page
0 margin

Attached the result inside maya.

Revision history for this message
Alvin Penner (apenner) wrote :

I think it would be best to raise this issue with the Maya developers, not with Inkscape.

Revision history for this message
Thomas Kaufmann (tkman) wrote :

as already mentioned, the fixes inside the eps do solve the issue.

The resulting eps is also far closer to what Illustrator is exporting.

I would highly doubt the Autodesk Developers would even consider changing anything to support open source inputs...

Revision history for this message
Alvin Penner (apenner) wrote :

alternatively, you could try an earlier version of Inkscape. attached is the result I get using Inkscape 0.91 r13725 (Jan 30 2015) and restricting the output to Postscript Level 2. This appears to contain only lines, no curves.
Does this work in Maya?

Revision history for this message
Thomas Kaufmann (tkman) wrote :

This is close to the result I am receiving when only changing the '/c' to '/l' inside the eps itself.
but still missing two points.

looking inside the file shows that there is only one point per line.
Is there no option to export them with cairo as "start_point(x,y) end_point(x,y) l "?

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.