Actually, John, it won’t report on either of those things you’ve mentioned. :)
What it does, however, is check every key & every value in every dictionary, and each element of every array in the Body of the PDF to make sure that their name, value, type, presence (or not) matches what it says in the spec. It also does the same for all content streams (whether page, XObject, AP, etc.). It also attempts to load every Font and ICC Profile that is referenced for at least basic validity. Leonard On 7/8/14, 3:50 PM, "John Hewson" <j...@jahewson.com> wrote: >That’s only going to find the most basic syntax errors though, such as a >dictionary with a missing >> or and object which ends without “endobj”. >It doesn’t check that the structure of the PDF is valid. > >I run the preflight syntax error check on almost every problematic PDF >which we get on JIRA and I’ve had it report an issue maybe twice. > >-- John > >On 8 Jul 2014, at 12:35, Leonard Rosenthol <lrose...@adobe.com> wrote: > >> Actually, preflight has an option called ³Report PDF Syntax Errors² >>which >> WILL check against ISO 32000-1 compliance - at least for the PDF body >> objects themselves. >> >> Leonard >> >> On 7/8/14, 2:02 PM, "John Hewson" <j...@jahewson.com> wrote: >> >>> On 8 Jul 2014, at 10:53, Martin Schröder <mar...@oneiros.de> wrote: >>> >>>> 2014-07-08 19:49 GMT+02:00 John Hewson <j...@jahewson.com>: >>>>> In Adobe Acrobat this file has only two pages, so as noted the root >>>>>of >>>>> the page tree is invalid: >>>>> >>>>> /Kids [3 0 R, 3 0 R, 3 0 R] >>>> >>>> This is IMHO perfectly valid. >>> >>> In cases like this where the spec is vague we rely on Acrobat¹s >>>behaviour >>> to decide what is and isn¹t valid. >>> >>>> Has anybody tried preflighting the pdf with Acrobat? >>> >>> Preflight can do some basic checks on ²standard" PDFs but it¹s really >>> limited, it¹s mostly for PDF/A, because the ²standard² PDF spec is too >>> vague to be used to verify conformance (many usable PDFs are >>> non-conformant anyway). >>> >>> -- John >> >
