You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
After an upgrade to version 1.2.4, scanning seems to work fine but after the ocr is done, I'm left with just a blank page and a couple of black bars. Every time I issue the "redo ocr" command, it shows me the document before returning to the blank image. I can just turn off OCR and everything works fine. My OS is an Ubuntu 18.04 and my OCR language is German.
Edit: paperwork also cannot figure out the orientation of the document any more and always assumes landscape.
The text was updated successfully, but these errors were encountered:
Some diagnostics: INFO paperwork.frontend.mainwindow.scan Failed to use OCR tool heuristic for orientation detection: 'KeyError' object has no attribute 'message' INFO paperwork.frontend.mainwindow Redoing OCR on 20180613_0737_06 p1 INFO paperwork.frontend.mainwindow.scan Will use tool 'Tesseract (sh)' WARNING paperwork.frontend.util.jobs Job OCR:0 took 2208ms and is unstoppable ! (maximum allowed: 500ms)
Edit: tesseract version: 4.00+git24-0e00fe6-1.2
AFAIK, Tesseract 4.00 is still in beta. Also it is currently not supported by PyOCR (see bug openpaperwork/pyocr#99 ).
I have no idea why some distributions (like Debian testing for instance) have already packaged Tesseract 4.
After an upgrade to version 1.2.4, scanning seems to work fine but after the ocr is done, I'm left with just a blank page and a couple of black bars. Every time I issue the "redo ocr" command, it shows me the document before returning to the blank image. I can just turn off OCR and everything works fine. My OS is an Ubuntu 18.04 and my OCR language is German.
Edit: paperwork also cannot figure out the orientation of the document any more and always assumes landscape.
The text was updated successfully, but these errors were encountered: