From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Scanning double sided documents and printing them the same.
Date: Thu, 10 Dec 2020 10:28:05 +0100 [thread overview]
Message-ID: <2156576.FFcC115b7c@eve> (raw)
In-Reply-To: <6c6ec963-5766-d0d8-c644-d5bbaaee6fcf@gmail.com>
On Thursday, December 10, 2020 1:09:29 AM CET Dale wrote:
> Howdy,
>
> I have a flatbed scanner. It's a old HP 4570. I been using Skanlite to
> scan pictures etc and it does a great job. On occasion tho I have a
> double sided document. I know how to scan them, scan one side, flip
> over and scan the back. That's easy enough. How do I print them the
> same way tho? Sometimes I use it like a copying machine basically.
> Scan in, then print. I'm not quite sure how to print the double sided
> stuff in one go tho.
>
> If someone does the same as me, can you share how you print them two
> sided? My printer is duplex so I just need to import both sides and
> tell it to print. I'm just not sure what software does that and makes
> it easy.
>
> Thoughts??
>
> Dale
>
> :_) :-)
My old printer/scanner can scan directly to PDF using the sheetfeeder.
For double-sided, I always ended up with 1 PDF with odd-pages and 1 with even.
There used to be tools available (python-old) that could shuffle these
together and merge them into a single PDF, which would allow for easy reading/
printing.
Currently, I would have to manually convert these to single-pages and then
merge them, again, manually.
This is the downside of single-sided sheetfeeders.
If you do the scans manually (eg. no sheetfeeders) you should be able to get
them all in the correct order in a PDF. The PDF can then be printed double-
sided and you get them the same way. (Just scan them "dummy-mode" and add
white-pages when the back of the sheet is white)
--
Joost
next prev parent reply other threads:[~2020-12-10 9:28 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
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 ` J. Roeleveld [this message]
2020-12-10 10:49 ` [gentoo-user] " 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=2156576.FFcC115b7c@eve \
--to=joost@antarean.org \
--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