Dear all,
As a PDF-import/export specialist, I created a relatively small PDF-file of only 4 KB named "Non-zero Yellow Mask Star set on Cyan rectangle positioned on Green background rectangle" which I've tried out in 8 different applications (see picture below). Most of these applications do agree, however with exception of CorelDRAW 2024: In the past some contributors of CorelDRAW Community have stated that CorelDRAW simply follows winding rules, and that these rules are hard to understand for most people. However, this does not explain differences of interpretation when opening a relatively small PDF-file with 8 different applications:
Included the relatively small PDF, so you guys are able to test:
PDF
Note: non-zero winding rule has been applied to the mask curve. In case of even-odd winding rule then the mask curve is equipped with a hole. In case a mask curve is used of which the fill does not depend on non-zero and even-odd winding rules then open functionality of CorelDRAW functions correctly.
Anybody experienced this problem?
Please adjust title: read winding instead of wining (slip of my pen).
Kind regards,
Jac.
While the winding rule may very well be important when you create the file (don't know, looks like it's exported from Easy Sign which I don't have), I doubt it is the reason something gets wrong when Draw tries to convert and open your file.The real reason seems to be that Draw misinterprets the clip mask, and that may be because of how EasySign exports it to PDF.If I open your PDF in Illustrator and then save it again without changing anything (I had to move all objects though because they were far away from the page, so I guess the PDF isn't all perfect), it looks fine when I open in Draw.Draw doesn't preserve the clip mask but at least it looks correct.
Thanks Ronny.
Your contribution is most welcome.
You wrote
"... that may be because of how EasySIGN exports it to EasySIGN."
I created a PDF-export file with Inkscape, and opened the PDF-export file of Inkscape in CorelDRAW.
CorelDRAW misinterprets this Inkscape PDF-file in the exact same way as the EasySIGN PDF-export file.
I could have used Illustrator, just as you did, but used Inkscape instead ;-)
Here's the Inkscape PDF-export file:
Now 8 out of 9 different applications tested happen to interpret the exact same document in a similar way. CorelDRAW applies a different interpretation.
Maybe both Inkscape as well as EasySIGN might be doing something wrong in their PDF-exports or they both do something which CorelDRAW is not able to swallow.
Strange.Did you recreate the file in Inkscape or did you import your EasySign PDF and then just resaved like I did in Illustrator?If so, maybe the "damaged" part was transferred from the PDF to Inkscape and then passed on to the new Inkscape PDF?If I take a closer look at these files in Draw, the black line is there but it is split up into two subcurves with two nodes each, and these two nodes are on top of each other, and there must be a reason why Draw converts the masked object into an impossible object.Not defending Draw, just trying to understand why it happens.
Small tutorial for Inkscape to reproduce problem:
Start with drawing a yellow star, starting at top, counterclockwise by using only 5 straight lines, followed by a cyan rectangle:
Select both objects and apply Set Clip:
Export to PDF and open PDF in CorelDRAW (misinterpretation):
Output in Adobe Acrobat:
PDF export file of Inkscape:
PDF export file of Inkscape (decompressed, thus readable):
More additional info in relation to the actual contents of the decompressed PDF-export of Inkscape:
It seems as if CorelDRAW at deep raw PDF-data level sees a "W* n" instead of a "W n" or simply applies its own default "W* n"?
This is really weird.But again, if I open one of your files in Illustrator and immediately saves it is PDF, it comes in fine in Draw after that.I think Illustrator replaces the clip mask with a real object, or uses a different code for the clip, one that Draw can interpret correctly.Anyway, I'll see if I can get someone from Corel to take a look at this thread, and maybe (not likely) get some information passed on to the ones that write the import filters.