Some input PDFs with Tesseract-OCR throw error in PyPDF2.utils.PdfReadError(Unexpected escaped string: b'{')' raised in ... about ocrmypdf HOT 5 CLOSED

Comment by jbarlow83
Mon Sep 7 20:14:52 2015

There's an error in the PDF file. I run qpdf to try to fix errors before anything else, but it can't fix everything.

You could "re-fry" the PDF with ghostscript, which rewrites and hopefully fixes the error. This has other side effects.
gs -o "$outpdf" -sDEVICE=pdfwrite "$inpdf"

pdftk also has a feature to fix damaged PDFs.

Can you provide a link to a sample? (Dropbox, etc.)

from ocrmypdf.

Comment by Wikinaut
Mon Sep 7 21:26:44 2015

@jbarlow83
great, because I wanted (but did not) to add some lines from my own project - but did not want to puzzle you with just another information.

Give me some time, I will try to find what went wrong (the scanned PDF was produced with gscan2pdf and tesseract. Perhaps I used already pdftk to merge some parts, and this step introduced the problem).

My own project (not published yet) creates single pages from a multi-page input pdf, converts them to single lossless-compressed images (png, not using convert but ghostscript), tesseract-ocrs (pdf rendering mode) page-by-page, and then uses pdftk to concatenate (re-merge) the single pages to the multi-page, double-layer output pdf. In that way, pdf errors are almost never coming up.

from ocrmypdf.

Comment by jbarlow83
Mon Sep 7 22:13:55 2015

I'd like the PDF because any errors get added to the test suite. I'm less interested in what produced the problem so much as trying to make sure all readable PDFs are accepted even if they are invalid.

Your project is quite similar to what this one does right now - just so you're aware. ocrmypdf converts pages to PNG uses ghostscript (btw: ImageMagick's convert also uses ghostscript, it just uses it badly), then uses tesseract for PDF rendering (optional with --pdf-renderer tesseract), and then uses ghostscript to merge. The error you ran into is in the first step, not later on in the pipeline.

Tesseract's PDF rendering has some issues (at least as of 3.03). It gets DPI wrong, it produces PDFs with syntax errors, and it can inflate file size in some situations. For those reasons --pdf-renderer tesseract is not the default. I'll be adding code to repair those problems or (more likely) extract the OCR layer from Tesseract's output and graft it into the final PDF, so that I can insert the text layer without transcoding any images.

from ocrmypdf.

Comment by Wikinaut
Mon Sep 7 22:35:32 2015

re. ghostscript vs. convert, yes, you are fully right. See http://bertanguven.com/faster-conversions-from-pdf-to-pngjpeg-imagemagick-vs-ghostscript/ .

And thanks for all the other infos.

BTW, I helped the tesseract people to fix a problem with the re-compression of the image (and I am proud, because it was difficult for some days). For a certain period, they lossy-re-compressed the input image (because the design goal was then to create minimal file sizes, which is a wrong goal), which introduced coding artefacts.

This is fixed since about one year, and current tesseract version are coding very well. When you now say, that Tesseract introduces PDF syntax errors, this explains my current issue. Thanks for info. Please, if you have further information why or when Tesseracts creates wrong PDFs, pls. report your observations upstream. They (user zdenop) will fix the issue.

Just for your information:

From my script the line where a pdf page is losslessy converted to an image (which is then input to tesseract, and rendered to pdf):

density = 400
image = yyy.png
file = zzz.pdf
## see http://bertanguven.com/faster-conversions-from-pdf-to-pngjpeg-imagemagick-vs-ghostscript/
gs -dNOPAUSE -sDEVICE=png16m -sOutputFile=$image -r$density -q $file -c quit

from ocrmypdf.

This is a Doublure of #19 .

from ocrmypdf.