Replies: 4 comments 4 replies
-
Investigating further will need:
|
Beta Was this translation helpful? Give feedback.
-
Thanks for the fast response. The version of ocrmypdf is 15.4.4 and of ghostscript 10.02.1. And these are the logs from paperless ngx/ocrmypdf: click here, to show logs
If I can provide any further information, let me know. - Thanks for help! |
Beta Was this translation helpful? Give feedback.
-
I couldn't reproduce the issue using your example file and ocrmypdf 16.3.0 veraPDF validated the output as PDF/A-2B. The command line I used was So it appears to me that the issue is due to old versions of ocrmypdf and/or ghostscript. |
Beta Was this translation helpful? Give feedback.
-
Ok, thanks for help and testing. - I think I have to look for a solution in the paperless ngx community, because everything runs in the Paperless Docker container and I can't do a manual update. |
Beta Was this translation helpful? Give feedback.
-
Hey there,
I'm using ocrmypdf within a paperless ngx (docker) installation, and it seems, that it is not able to produce reliable pdf/a files. If I run a validation check (e.g. with verapdf) it always fails. I can not find any logs, that would show me, that the pdf/a conversation doesn't work correctly:
I already tried several specific pdf/a settings (e.g. pdfa-2) in the docker-compose file environment and in the webgui settings for testing, but without success.
Could anybody help me with this issue? What could be a reason for the not correct creating/archiving pdf/a files?
Thanks for help in advance - Daniel
Beta Was this translation helpful? Give feedback.
All reactions