"I have built a document management system for home use. I did research on the above. I love JPEG2000 because it’s in PDF. Today you have high quality javascript renderers that can show PDF including the JPEG2000. The only REAL problem I found was the scaling limit on the various linux and windows renderers."
In today's #wtfPDF news - Foxit integrates #ChatGPT into #PDF Editor Cloud, use cases include "have a conversation with PDF and answer user questions based on PDF content"😱:
I explored to what extent #VeraPDF and #JHOVE can be used to identify #PDF features that are potential preservation risks. Check out this (massive!) blog post for the full lowdown #wtfPDF:
Aight. so i'll take out a bit of time today to try to trouble-shoot a PDF validation error. Stressing "try" here, in my experience this is rarely completed successfully. thought i'd share some steps here to see if other's have input.
JHOVE error du jour is:
PDF-HUL-104 Expected dictionary for font entry in page resource
🧵 below (if i manage to operate mastodon correctly, that is).
So to summarize the story so far .... we've moved from 1 error reported by JHOVE and a different one reported by pdfcpu (and none by qpdf) to 8 font syntax errors with pdffonts and 76 font errors with Adobe Preflight.
The logical summary so far is of course #wtfPDF
I shall continue to dig deeper later on. Now off to meetings for the rest of the afternoon!
as we learned ⬆️ the font problem is on page 2 / obj 6. with
pdf-parser -o 6 filename.pdf
we can take a quick look at the content of obj 6.
This returns an odd Font dictionary, that lists 4 names (/F16, /F18, /F26, /F28, /F36, /F38) with "null" instead of the expected indirect object.
which makes them a bit hard to find, to put it nicely.