-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Do not modify files that had no OCR done #130
Comments
Hi @doppelgrau, i think the problem here is that the app just processes a PDF file matching your workflow settings and does not analyze the output. Also i'm not sure if there's a reliable way to detect if |
Took a look on the documentation, if you run it without any of the options (--skip-text, --redo-ocr, force-ocr) the returncode 6 would indicate that:
So there is only an easy way if combined with #129 to allow none of these options to be used. |
Interesting, thanks for your efforts. So to explicitly check for an exitcode Ping @bahnwaerter for contact, we'll report our results here. Thank's for your patience. |
I agree, checking if something had changed would be nicer. But found no nice way with ocrmypdf, so the "returncode 6 solution" might be a compromise. With |
Thank's @doppelgrau, the hint for the So a solution could be to always use the Just to pin this down for me:
|
This is a very difficult task if this should be solved outside of One possibility to get the information is mentioned by @doppelgrau in a comment above and addresses the checking of The idea mentioned by @doppelgrau in a comment above is another possibility to get the information by parsing and checking the output of the A third solution proposed by @R0Wi in the comment before makes use of the I suggest to implement this new feature with the third proposed solution from @R0Wi. The functionality of this solution does not break the existing behavior of this workflow app if it's configurable by an optional workflow option. So, I agree with @R0Wi's personal bullet points to implement this requested feature. |
Only create new file version if OCR result was not empty Signed-off-by: Robin Windey <[email protected]>
Only create new file version if OCR result was not empty Signed-off-by: Robin Windey <[email protected]>
Only create new file version if OCR result was not empty Signed-off-by: Robin Windey <[email protected]>
Only create new file version if OCR result was not empty Signed-off-by: Robin Windey <[email protected]> Signed-off-by: Robin Windey <[email protected]>
Only create new file version if OCR result was not empty Signed-off-by: Robin Windey <[email protected]> Signed-off-by: Robin Windey <[email protected]>
Only create new file version if OCR result was not empty Signed-off-by: Robin Windey <[email protected]> Signed-off-by: Robin Windey <[email protected]>
Only create new file version if OCR result was not empty Signed-off-by: Robin Windey <[email protected]> Signed-off-by: Robin Windey <[email protected]> Signed-off-by: Robin Windey <[email protected]>
Only create new file version if OCR result was not empty Signed-off-by: Robin Windey <[email protected]> Signed-off-by: Robin Windey <[email protected]> Signed-off-by: Robin Windey <[email protected]>
Hello,
I just observed, that files where no additional OCR is done were still shown as a changed and new version in nextcloud.
Would be a bit nicer in my eyes, if in that case the file is not modified. (Not "cluttering" the file history and maybe preserve other stuff like digital signatures.)
Don't know if that can be easily done and/or there are other reasons to keep this behavior.
Thanks for your work so far.
The text was updated successfully, but these errors were encountered: