Hi Craig,
if you create a report by adding the --report switch to the command
line call you will get further explanation about the type of error,
what kind of objects are affected, why this is an error and how it
could possibly avoided. Use pdfaPilotConverter --help in order to get
further information what additional parameter the --report switch may
take (e.g. there are two report types either XML or HTML with many
more options).
You may as well use pdfaPilot Convert in order to fix problems like
the one you are mentioning.
Thanks,
Dietrich
Hi,
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?
Regards,
Craig Broadbear
CEO Broadgun Software
_______________________________________________
callas_user_forum mailing list
callas_user_forum(a)lists.callassoftware.com
http://lists.callassoftware.com/mailman/listinfo/callas_user_forum
--
Dietrich von Seggern | Director Product Management
callas software GmbH | Schoenhauser Allee 6/7 | 10119 Berlin | Germany
Tel +49.30.4439031-0 | Fax +49.30.4416402
Amtsgericht Charlottenburg, HRB 59615 | Geschaeftsfuehrung: Olaf
Druemmer, Ulrich Frotscher