Bug 693322 - Acrobat Preflight tool reports missing XObjects
Summary: Acrobat Preflight tool reports missing XObjects
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Writer (show other bugs)
Version: 9.06
Hardware: PC Windows 7
: P4 normal
Assignee: Ken Sharp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-07 16:04 UTC by Lev Bishop
Modified: 2013-11-07 02:39 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---

Attachments
input file (10.06 KB, application/pdf)
2012-09-07 16:04 UTC, Lev Bishop 		Details
output from gs 9.6 (11.67 KB, application/pdf)
2012-09-07 16:05 UTC, Lev Bishop 		Details
report from preflight tool (12.12 KB, text/plain)
2012-09-07 16:05 UTC, Lev Bishop 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lev Bishop 2012-09-07 16:04:50 UTC 
Created attachment 8917 [details]
input file

Use Adobe Acrobat X Pro version 10.1.4 preflight tool, with the "Report PDF Syntax issues" profile.

Input file cavendish.pdf reports no issues.
Run through ghostscript 9.6 as follows:

gswin64c -q -dNOPAUSE -dBATCH -dSAFER -sOutputFile=cavendish_gs.pdf -dCompatibilityLevel=1.5 -sDEVICE=pdfwrite cavendish.pdf

Output file cavendish_gs.pdf reports missing XObjects R20, R26, R29 and missing extended graphics state R15.

Input and output pdfs attached as well as preflight report.
Comment 1 Lev Bishop 2012-09-07 16:05:23 UTC 
Created attachment 8918 [details]
output from gs 9.6
Comment 2 Lev Bishop 2012-09-07 16:05:49 UTC 
Created attachment 8919 [details]
report from preflight tool
Comment 3 Ken Sharp 2012-09-13 15:13:42 UTC 
The preflight tool is not inheriting the Resources from the Page object when evaluating the Pattern object(s).

Technically, yes, this is an error, but all PDF consumers happily inherit the Resources from the Page object when evaluating objects on the the page.

*** This bug has been marked as a duplicate of bug 691522 ***
Comment 4 Lev Bishop 2012-09-13 15:30:26 UTC 
(In reply to comment #3)

> Technically, yes, this is an error, but all PDF consumers happily inherit the
> Resources from the Page object when evaluating objects on the the page.

Apparently not all PDF consumers will happily inherit this. See this discussion http://tex.stackexchange.com/q/70355/627 where an on-demand book printer failed a job because of this issue.
Comment 5 Ken Sharp 2012-09-13 15:41:48 UTC 
(In reply to comment #4)
> (In reply to comment #3)
> 
> > Technically, yes, this is an error, but all PDF consumers happily inherit the
> > Resources from the Page object when evaluating objects on the the page.
> 
> Apparently not all PDF consumers will happily inherit this. See this discussion
> http://tex.stackexchange.com/q/70355/627 where an on-demand book printer failed
> a job because of this issue.

Then I refer to the mantra which gets used against us all the time 'Acrobat is happy with it'.
Comment 6 Ken Sharp 2013-11-06 01:19:55 UTC 
Commit 616ff4cc44b00bcf7df97b64c8bdaebbe0620713 fixes all the XObject parts of this report. However there is still a missing ExtGState which needs to be addressed seperately.
Comment 7 Ken Sharp 2013-11-07 02:39:01 UTC 
And the ExtGState is fixed with commit cfeb9f98b896384ac366f4e30f3653a52de7af87