Feature request #1569
Description
In our company, we use verapdf in a script compiling tex to pdf and thereafter verify PDF/A and PDF/UA with verapdf.
To have overview, we need verapdf --format text xxx.pdf but we must also document which verifyer has been run.
To that end, we invoke verapdf --format html xxx.pdf > $target-validationReport.html.
This is vital because the validation report informs about which version of verapdf has been run and also the build date.
Moreover, which standards were checked.
This report is archived together with the document itself.
Currently, we invoke verapdf twice, once to get the rough result on the console (just 4 lines)
and then to get the full report in html format.
This is waste of time.
I think there should be more companies which work like that.
Our suggestion: allow
verapdf --format text --format html --output xxx-validationReport.html xxx.pdf
which means validating xxx.pdf once and outputting the result in the given formats,
- text as a text since no --output given on the console.
- html in a file given by --output.
I can imagine that in parallel json for further processing could be of some interest.
An alternative: --output substitutes for --format, the format just reading off the ending.
txt means text.