Search Criteria
Package Details: pdfsandwich 0.1.7-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/pdfsandwich.git (read-only, click to copy) |
---|---|
Package Base: | pdfsandwich |
Description: | Wrapper for tesseract OCR and hocr2pdf to generate pdf files with the recognized text put behind the image (sandwich pdfs). |
Upstream URL: | http://sourceforge.net/projects/pdfsandwich/ |
Licenses: | GPL2 |
Submitter: | petRUShka |
Maintainer: | petRUShka (whnr) |
Last Packager: | whnr |
Votes: | 16 |
Popularity: | 0.000000 |
First Submitted: | 2016-11-17 16:52 (UTC) |
Last Updated: | 2018-09-23 15:00 (UTC) |
Dependencies (7)
- imagemagick (imagemagick-gitAUR, imagemagick-full-gitAUR, imagemagick-fullAUR)
- poppler (poppler-gitAUR)
- tesseract (tesseract-gitAUR)
- unpaper (unpaper-gitAUR)
- gawk (gawk-gitAUR, busybox-coreutilsAUR) (make)
- ocaml (make)
- ghostscript (optional) – Ghostscript is only needed for resizing pdf pages, if the respective command line option is given.
Latest Comments
1 2 Next › Last »
allexj commented on 2022-05-07 08:46 (UTC)
If you have the error:
I/O Error: Couldn't open file '/tmp/pdfsandwich_tmpcaa21c/pdfsandwich2ca1bb.pdf': Too many open files. Syntax Error: Could not merge damaged documents ('/tmp/pdfsandwich_tmpcaa21c/pdfsandwich2ca1bb.pdf')
during pdfunite command, you have to increase the max number of open files. It's easy.
More info here: https://www.mariogiannini.com/2018/11/03/too-many-files-open/ or https://unix.stackexchange.com/questions/85457/how-to-circumvent-too-many-open-files-in-debian or https://subvisual.com/blog/posts/2020-06-06-fixing-too-many-open-files
whnr commented on 2022-04-16 14:12 (UTC) (edited on 2022-04-16 14:15 (UTC) by whnr)
Yes! Something is broken with
unpaper
. If you already have decent scanned input, you can convert it by skipping that component with the-nopreproc
option.If this functionality is needed you can try this workaround: https://github.com/Ra-Na/pdfsandwich-without-unpaper
Danyright commented on 2022-04-13 14:15 (UTC) (edited on 2022-04-13 14:15 (UTC) by Danyright)
With a recent system update I did, pdfsandwich now generates an (almost) completely black PDF. I tested with multiple pdf files with multiple images as source, but I can't get it to work properly. I tested on two different computers with similar issues.
Anyone experiencing the same problems? Does anyone have a solution ?
Thanks for the help, D
petRUShka commented on 2018-09-21 09:19 (UTC)
Please welcome whnr as our new maintainer.
Thanks to all for your help and notices!
whnr commented on 2018-09-19 17:07 (UTC) (edited on 2018-09-19 17:10 (UTC) by whnr)
Here is a patch to update the PKGBUILD to 0.1.7. Ghostscript is now optional. I'll also email petRUShka directly.
Maxr commented on 2018-08-14 10:28 (UTC)
Now it is, 0.1.7 was just released, see https://sourceforge.net/projects/pdfsandwich/files/
benoliver999 commented on 2018-02-12 16:43 (UTC)
I agree, this package is not out of date.
seifferth commented on 2018-01-28 00:16 (UTC)
HaoZeke: I encountered the same error when building exact-image. Note however, that this error occurs when compiling exact-image, not when compiling pdfsandwich. Out of curiosity I modified the PKGBUILD and simply removed the exact-image dependency, which caused pdfsandwich to build, install and (preliminary testing suggests) also work without problems.
Which leads to the following question: Why is exact-image included as a dependency? Since it doesn't seem to be vital I'd suggest to rather include it as an optional dependency:
That way the problems exact-image is having wouldn't directly effect this package.
Also: From what I can see this package is up to date with upstream, so it shouldn't be flagged out of date.
Best Regards and thanks to petRUShka for the package.
HaoZeke commented on 2018-01-18 17:30 (UTC)
Somehow broken currently..
Log:
petRUShka commented on 2017-03-09 18:36 (UTC)
1 2 Next › Last »