[gs-bugs] [Bug 698765] - Ghostscript - PDF/X Compliance Check Fails with Ghostscript generated PDF

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698765

Bug ID: 698765
Summary: PDF/X Compliance Check Fails with Ghostscript
generated PDF
Product: Ghostscript
Version: unspecified
Hardware: PC
OS: All
Status: UNCONFIRMED
Severity: major
Priority: P4
Component: General
Assignee: ghostpdl-***@artifex.com
Reporter: ***@gmail.com
QA Contact: gs-***@ghostscript.com
Word Size: ---

Created attachment 14473
--> http://bugs.ghostscript.com/attachment.cgi?id=14473&action=edit
Sample files

Hi,

PDF/X-3:2003 compliance test fails with Ghostscript generated output.

This is the command I am using -

"C:\Program Files\gs\gs9.22\bin\gswin64c.exe" -dPDFX -dSAFER -dBATCH -dNOPAUSE
-dNOPROMPT -dNOOUTERSAVE -sProcessColorModel=DeviceCMYK -dSubsetFonts=false
-dEmbedAllFonts=true -r300 "-dPDFSETTINGS=/default " -sDEVICE=pdfwrite
-sOutputFile=Output.pdf PDFX_def.ps -- Input.pdf

We use 9.06, but the issue occurs with latest version as well.

Attaching input, output, compliance screenshot, and my PDFX_def.ps (it is a
default file only, I have just commented out 'ICCProfile (ISO Coated sb.icc)'
line to make it work, no other change).

Can you please check ?

Thanks,
Rajiv

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698765

Ken Sharp <***@artifex.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Component|General |PDF Writer
Assignee|ghostpdl-***@artifex.com |***@artifex.com
Severity|major |normal

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698765

Ken Sharp <***@artifex.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Ken Sharp <***@artifex.com> ---
You command line looks wrong to me;

For starters you are using PDFSETTINGS, you really do *not* want to do that
while at the same time using PDFA or PDFX. If you understand what you are doing
you can, with care, change some of the default settings individually to control
some aspects of the output PDF file, but changing the settings wholesale like
this is simply not going to work.

You do not need to set (and should not set) SubsetFonts or EmbedAllFonts when
using either PDF/X or PDFA switches. PDFA and PDFX set up the device correctly
for the relevant selected output. Altering some controls will result in
non-compliant output. Also note that selecting PDFSETTINGS *after* other
controls (whose values are affected by PDFSETTINGS) will cause those controls
to be overwritten with the values from the selected PDFSETTINGS.

You should not use -dNOOUTERSAVE, I don't know what you think that's doing, but
I bet it isn't doing what you think it is. This switch should only be used in
conjunction with the job server, which you are not using.

You do not need -- when the remaining arguments are all input filenames or when
there is only one argument (as is the case here)

Using this command line:

gswin32 -dPDFX -dPDFACompatibilityPolicy=1 -sProcessColorModel=DeviceCMYK
-sColorConversionStrategy=CMYK -sDEVICE=pdfwrite -sOutputFile=out.pdf
PDFX_def.ps Input.pdf

with your PDFX_def.ps file and your input.pdf does reveal one small problem,
there's a typo in the code to check whether an annotation is on the page
(off-page annotations are permitted i PDF/X). I've fixed that in commit

cea5d8a72dab953fe84ab8f7280003d377559fff

The file produced using the command line above then passes preflight checks in
Adobe Acrobat for me.

[b***@artifex.com]

http://bugs.ghostscript.com/show_bug.cgi?id=698765

--- Comment #2 from Rajiv <***@gmail.com> ---
Thanks Ken for quick response.

Would it be possible for you to share the fixed output ?

Regards,
Rajiv