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
Hi,
I am running Nextcloud 21 with Full text search, Full text search - Elasticsearch Platform, Full text search - Files all with version 21.0.0 and Full text search - Files - Tesseract OCR with version 20.0.1
All is running in a docker container from the official base image with additional installation of tesseract, tesseract-deu, ghostscript and ImageMagic-7 and I modified the policy so that it can read and write pdfs.
For some of my pdfs I get the following exception. Workaround at the moment is moving them into a separate folder with .noindex in it. That is of cause just a ugly workaround It seams that the OCR could find something and that's why the second parameter here is null. Wouldn't it be better if there is a kind of try expect / try-catch around that and if you can't index a single file, ignore it and go to the next.
Hi,
I am running Nextcloud 21 with Full text search, Full text search - Elasticsearch Platform, Full text search - Files all with version 21.0.0 and Full text search - Files - Tesseract OCR with version 20.0.1
All is running in a docker container from the official base image with additional installation of tesseract, tesseract-deu, ghostscript and ImageMagic-7 and I modified the policy so that it can read and write pdfs.
For some of my pdfs I get the following exception. Workaround at the moment is moving them into a separate folder with .noindex in it. That is of cause just a ugly workaround It seams that the OCR could find something and that's why the second parameter here is null. Wouldn't it be better if there is a kind of try expect / try-catch around that and if you can't index a single file, ignore it and go to the next.
An unhandled exception has been thrown:
Is there somehow a possibility to ignore a single file, so that I don't have to move them?
The text was updated successfully, but these errors were encountered: