(I use this feature every day, multiple times a day, to export vector line art to PDF files - and have NEVER had this issue until now).
All vector lines are being transformed into bitmap rendered line segments (they are several pixels wide and have gradations in shading within the width and length of the lines). No options available under 'Publish to PDF/Settings' dialog box to remedy this issue. Tried every option under the 'PDF Preset' dropdown (Archiving, prepress, document distribution, etc), but that did not fix the issue. The dialog box also shows "1 Issue detected in document', this issue is 'there are fonts below 18pt in your document'. I don't know why that would affect the vector lines, but it's worth noting as I did not have this issue before the update.
Work-around: The only work-around I have found is to use the 'Print' command, then change printer to 'Adobe PDF'. This results in vector lines remaining in the final pdf, not being converted into bitmap. This is, however, not the same as Publish to PDF, and takes significantly longer to 'Print' the file (ie, it's not an ideal workaround).
Thank you KRLightning.I'm glad I could help and also very glad to hear you found the cause to why the objects had a transparency.As Bobby mentioned, transparencies can be very unpredictable when exporting and some features in Draw's transparencies may not have an equivalent in the PDF file format, so all they can do is to convert to a bitmap, which of course isn't ideal.
This one interested me because of two things, the small size of the outlines and the transparency. I have had zero issue with CorelDRAW transparency in output and as such I decided to test transparency in fills and larger sized outlines.
I'm thinking that it may be transparency combined with the small size of the strokes/objects. There was a post just recently where the issue was small objects being rasterized incorrectly. I'm wondering if it's that error combined with transparency.
In the capture below there are 4 stacked layers of transparency including both CMYK and spot colors. While this is live transparency and should only be attempted in a true PDF RIP, I found that the RIP handled it properly and even as a round trip CorelDRAW process CorelDRAW imported its own PDF correctly. The orange square is actually the red square with a different outline and a transparency applied, the red square has a spot color drop shadow.
The importation filter being highly suspect, I wonder if one can create the issue with an all native CorelDRAW file?
I did some more testing on fine lines converted to objects. You can reproduce errors in PDF rendering with a RIP viewed and round-trip PDF in CorelDRAW. The magenta rectangle has 6 objects created as outlines in .001", .004" and .007", then converted to objects.
The bottom left 3 had normal merge lens applied directly to the original object and when published to PDF they remain vectors.
The bottom right 3 had the objects copied and pasted on top and the lens applied to the top copy only with if darker merge applied and when published to PDF, they became palleted bitmaps.
The top left 3 were the original objects, far right and middle with an if darker merge applied, the far left remained a vector, broke apart and became partially invisible, the middle became a palleted bitmap. The far right had a subtract lens applied, it remained a vector and had a significant color shift.
I have used the normal merge significantly and multiply quite a bit with zero issues.
yes thanks for sharing
David Milisock said:I'm thinking that it may be transparency combined with the small size of the strokes/objects.
I suspect it has to do with the transparency's merge mode.As long as you use a "Normal" or "Multiply" transparency (there may be others too), it will be treated as a lens object.If you choose for example "If Darker" (as in this file), it will be converted to a bitmap instead.So, my guess is that the PDF file format cannot handle all the merge modes in Draw, or at least not in a way that can be easily translated between the two.