|
|
Screen Shot 2021-03-16 at 07.34.47.jpg (241,295 bytes) |
|
|
Looks like a bug in PDF checkpoint. Afaik the mentionned key is specific to PDF/X-1. |
|
|
With PDF/X files from other publishing software this does not happen. They do have a PDF/X key. |
|
|
The GTS_PDFXConformance key is only mandatory for PDF/X-1a. This is confirmed by Medatata section at page 21 of http://www.eci.org/_media/downloads/pdfx/pdfx_faq_english_nov05.pdf. So I confirm this is a bug in PDF Checkpoint. |
|
|
Fyi the documentation of Callas pdfToolbox also specifies they perform the check for GTS_PDFXConformance key only for PDF/X-1a version 2001. See page 326 of https://www.impressed.de/DOWNLOADS/pdfToolbox_Desktop/callas_pdfEngine_Reference.pdf |
|
|
Not to mention Acrobat itself and Pitstop are both validating our PDF/X-3 output. |
|
|
Btw the message of PDF Checkpoint shows itself their analysis is buggy as it mentions PDF/X-3:2003 while we export to the older PDF/X-3:2002. PDF/X-3:2003 uses PDF 1.4 as a base while PDF/X-3:2002 is based on PDF 1.3. |
|
|
Thank you very much for testing it. Don't get me wrong, I am not a programmer, I am just a user, and I am using Scribus for 10 years now without any problems. Just recently I purchased Affinity Publisher (huge discount), to see if it can simplify my work. In some points for the current project yes, but unfortunately it does not embed a profile in the PDF, so the print company rejected the job. So I searched for a PDF checker and — of course — tested some Scribus PDF files. I thought it might be good to communicate a possible problem. And yes, I still use Scribus, I've even rebuilt the current project in Scribus to get the job done. My intention is not to complain about anything, but to eventually improve the program by communicating a possible problem or bug. Again, thanks for looking into the case. I will just keep using Scribus without any further checking. |
- Anonymous
