View Issue Details

IDProjectCategoryView StatusLast Update
0016517ScribusPDFpublic2021-03-16 21:42
Reportertoyotadesigner Assigned Tojghali  
Status closedResolutionno change required 
PlatformmacOSOSCatalinaOS Version10.15.7 (19H524)
Product Version1.5.7.svn 
Summary0016517: Missing PDF/X key
DescriptionI am currently testing »PDF Checkpoint«, a software for macOS that checks an exported PDF for errors. No, I do not test this software to verify Scribus generated PDF documents, but to check PDF documents from another publishing software. However, I dragged a Scribus PDF document into the software and got a warning: Missing PDF/X key: PDF/X-3 (2003)

Would it be possible if the developers could check this feature and include it in future releases?
Steps To ReproduceJust export a PDF/X-3 file and check it
TagsNo tags attached.



2021-03-16 07:11



2021-03-16 10:03

administrator   ~0048941

Last edited: 2021-03-16 10:04

Looks like a bug in PDF checkpoint. Afaik the mentionned key is specific to PDF/X-1.


2021-03-16 11:04

reporter   ~0048942

With PDF/X files from other publishing software this does not happen. They do have a PDF/X key.


2021-03-16 19:59

administrator   ~0048944

Last edited: 2021-03-16 20:02

The GTS_PDFXConformance key is only mandatory for PDF/X-1a. This is confirmed by Medatata section at page 21 of So I confirm this is a bug in PDF Checkpoint.


2021-03-16 20:44

administrator   ~0048946

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


2021-03-16 20:45

administrator   ~0048947

Not to mention Acrobat itself and Pitstop are both validating our PDF/X-3 output.


2021-03-16 20:51

administrator   ~0048948

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.


2021-03-16 20:58

reporter   ~0048949

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.

Issue History

Date Modified Username Field Change
2021-03-16 07:11 toyotadesigner New Issue
2021-03-16 07:11 toyotadesigner File Added: Screen Shot 2021-03-16 at 07.34.47.jpg
2021-03-16 10:03 jghali Note Added: 0048941
2021-03-16 10:04 jghali Note Edited: 0048941
2021-03-16 11:04 toyotadesigner Note Added: 0048942
2021-03-16 19:59 jghali Note Added: 0048944
2021-03-16 20:00 jghali Note Edited: 0048944
2021-03-16 20:02 jghali Note Edited: 0048944
2021-03-16 20:44 jghali Note Added: 0048946
2021-03-16 20:45 jghali Note Added: 0048947
2021-03-16 20:51 jghali Note Added: 0048948
2021-03-16 20:58 toyotadesigner Note Added: 0048949
2021-03-16 21:41 jghali Category Import / Export => PDF
2021-03-16 21:41 jghali Description Updated
2021-03-16 21:41 jghali Assigned To => jghali
2021-03-16 21:41 jghali Status new => resolved
2021-03-16 21:41 jghali Resolution open => no change required
2021-03-16 21:42 jghali Status resolved => closed