I am interested in using pdfaPilotValidator for testing PDF/A compliance.
It spits out a lot of messages, "hits", however it does not provide any
details on what part of the PDF file it is referring to. Is there any way
to get this info? e.g. a byte offset into the PDF, or a at least a PDF
object number and maybe a "snippet" of PDF operators.
Are the messages, such as "Device-dependent color exists, but no output
intent" further explained somewhere?
Also, is there a list of checks that the pdfaPilotValidator performs?
CEO Broadgun Software