From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Scanning double sided documents and printing them the same.
Date: Thu, 10 Dec 2020 09:26:01 +0000 [thread overview]
Message-ID: <20201210092601.356650a4@digimed.co.uk> (raw)
In-Reply-To: <2180124.ElGaqSPkdT@lenovo.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
On Thu, 10 Dec 2020 09:20:22 +0000, Michael wrote:
> > Gscan2pdf has lots of nice features, I used to use it with an ADF and
> > it would scan all the sheets, then I'd turn the stack over and feed
> > it back in and it would scan the other sides and then put all the
> > pages in the correct order.
> >
> > I have a duplex scanner now, but that was a real time saver.
>
> Alternatively, on the CLI you could use imagemagick to convert your
> png, tiff, jpg, etc., to pdf:
>
> convert scan1.png scan1.pdf
> convert scan2.png scan2.pdf
>
> Then join the two pdf documents into one with two pages, using
> poppler's pdfunite:
>
> pdfunite scan1.pdf scan2.pdf scanned.pdf
>
> Then print them.
>
> A simple script could batch up the conversion for you, e.g.:
>
> for file in $(ls -t *.png | head -8); do
> convert $file $file.pdf
> done
>
> The above will convert 8 png files to pdf, which you can then pdfunite
> into a single multipage pdf document before you print it.
That's pretty much what I used to do. The nice thing about gscan2pdf's
way of doing it is that it copes with the second sides being scanned in
reverse order if you use an ADF. You could script that, but when someone
has already done it, laziness... I mean efficiency, wins.
--
Neil Bothwick
Anything is possible if you don't know what
you are talking about.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-10 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 0:09 [gentoo-user] Scanning double sided documents and printing them the same Dale
2020-12-10 0:46 ` thelma
2020-12-10 1:29 ` thelma
2020-12-10 2:16 ` Dale
2020-12-10 8:27 ` Neil Bothwick
2020-12-10 9:20 ` Michael
2020-12-10 9:26 ` Neil Bothwick [this message]
2020-12-10 15:21 ` [gentoo-user] " Grant Edwards
2020-12-10 17:36 ` Michael
2020-12-10 22:25 ` Grant Edwards
2020-12-11 0:00 ` Dale
2020-12-11 0:04 ` Dale
2020-12-10 9:28 ` [gentoo-user] " J. Roeleveld
2020-12-10 10:49 ` Dr Rainer Woitok
2020-12-10 13:09 ` J. Roeleveld
2020-12-10 15:37 ` Rich Freeman
2020-12-10 17:58 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201210092601.356650a4@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox