Peter Wyatt

Hi @ESultanik, I’ve been promoting something similar (a “heat map” of file reads) for a while… I see the following benefits: - Visualize what a given parser reads/processes vs what...

Sure (thinking of something like no xref) - do you have a 'short-list' of parsers you prefer?

[polytracker.zip](https://github.com/trailofbits/polytracker/files/4680833/polytracker.zip) I hand-made some samples for you by hex-editing down a PDF: no xref, no startxref, no trailer, etc. Filenames are descriptive of the malform. QPDF certainly outputs different warning...

You might consider plumbing in an Output Intent with a monochrome ICC profile, much like the MacOS print pipeline did (does?)...

Again, this was a hand-edited PDF because I can't share the real-world PDF. My issue reduced down to a cause of "%PDF-1.x" vs "%PDF-2.0" in the first line header comment....

Thanks for considering. If/when you get around to thinking more about it, please reach out if you have any questions. Will give it a go... (pun intended).

@kpym Because PDF 2.0 introduced new basic UTF-8 string type as well as AES-256 and Unicode passwords. So a PDF 1.x can generally be "re-versioned" up to PDF 2.0 by...

@kpym Yeap - definitely part of it, as is checking the current implementation against the far more detailed and precise definitions that PDF 2.0 defines for many aspects of syntax,...

That 'cos Edge uses Adobe nowadays: https://blogs.windows.com/msedgedev/2023/02/08/adobe-acrobat-microsoft-edge-pdf/

Hi @hhrutter, Yes, my usage is via command line: `pdfcpu validate --mode=strict file.pdf`. Depending on other users and use-cases, I would be happy to either use `--mode=strict` or have an...