Flow for Preflighting InDesign files
Posted: Tue Feb 19, 2019 12:55 am
I am sure several of you have ran into this issue and have come up with a solution. To preflight an InDesign file a PDF needs to be exported in order for Pitstop to preflight it. The problem is if an image or font is missing it is not reflected on the PDF or preflight (unless I am missing something). The font gets substituted and the image is the low res proxy. I know I can set it up to stop/fail when it runs in to this problem but I want it to report the missing fonts and images (kind of defeats the purpose of an automated workflow).
My question is how is everyone else handling this issue? As of right now I am thinking of three potential ways to with scripting, text files, and XML.
--Have InDesign export it's own preflight as a text file and parse the data to be added later to the Pitstop report (I have created a custom preflight report)
--Have InDesign export it's own preflight report as a PDF then export the PDF as XML and combine later with the Pitstop report
--Have a javascript pull the info from InDesign and add it later to the Pitstop report
Is there a more sophisticated way to achieve this or am I on the right track here?
Thanks,
My question is how is everyone else handling this issue? As of right now I am thinking of three potential ways to with scripting, text files, and XML.
--Have InDesign export it's own preflight as a text file and parse the data to be added later to the Pitstop report (I have created a custom preflight report)
--Have InDesign export it's own preflight report as a PDF then export the PDF as XML and combine later with the Pitstop report
--Have a javascript pull the info from InDesign and add it later to the Pitstop report
Is there a more sophisticated way to achieve this or am I on the right track here?
Thanks,