6 ms·
Amazing share on the tooling side of thing for PDF processing. More on PDF and why it's hard to do analysis [1]. TL;DR "PDF was never really designed as
by devy 4y ago
Amazing share on the tooling side of thing for PDF processing.
More on PDF and why it's hard to do analysis [1]. TL;DR
"PDF was never really designed as a data input format,
but rather, it was designed as an output format
giving fine grained control over the resulting document."
By the way, the PDF 1.4 (most widely used version) specification is over 1000 pages![2] To make it even harder, not everybody follow the spec :)
[1] https://news.ycombinator.com/item?id=33146364 https://news.ycombinator.com/item?id=33146364
[2] https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/pdfreference1.4.pdf https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandard...
- bee_rider 4y agoYeah I think 95% of the time, the correct way to fix a problem with a PDF is to go back to the tool that generated it, and fix the issue in the input. But, sometimes non-ideal circumstances intervene.
- perelin 4y agoMake that 99%
- jimjimjim 4y agoyes, until very recently, if what adobe acrobat/reader did was different to the spec then the spec was wrong. Very hard to tell a client that their document is corrupted when they can read it just fine in adobe.