Neil Percy
My feedback
1 result found
-
3 votes
An error occurred while saving the comment An error occurred while saving the comment Neil Percy commentedThe reason why the PDF shell is because as long as you have compatible turned on you can just keep working in Illustrator and then just save the file, once this is done Esko is connected to your servers and folders so you can see your file and just run the workflows.
If you were going to export a PDF, you would be working in Illustrator, then finish your work, then have to export out as a PDF to run your workflows.
The software is set up to be process driven so the first way does this, the second way is not process driven at all. By the way I get the same problem when exporting out as a PDF as well.
Here are some images to show you how the Illustrator file looks compared to what the PDF shell looks like.
An error occurred while saving the comment Neil Percy commentedThe reason why we use the PDF shell of the Illustrator file is because of a packaging application the industry uses called Esko Automation Engine. We do all our work in Illustrator and then save the file with compatible turned on. We then use Esko AE to run workflows and for this to happen it uses the PDF shell.
Would you like me to send you the file in question, so you can see how the text is made up? I will not be able to send you the fonts but a least you can see how the text is done?
An error occurred while saving the comment Neil Percy commentedHi Lance, It does. The pdf shell of the Illustrator file converts the stroke of the text to outline while keeping the main body of the text live.
Neil Percy shared this idea ·
Thank you for understanding. It's been nice virtually dealing with you.
Let's hope the dev team look at this and thinks it's a good idea to progress with.