From: "Glenn" <glennervin@cableone.net>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: Scanning
Date: Fri, 6 Nov 2015 07:49:56 -0600 [thread overview]
Message-ID: <FCA4A842C8784E97A3FCCCF581070EAD@LennyAcer5720> (raw)
In-Reply-To: <563C812C.5000807@baechler.net>
That may have to do with too much resolution picking up too many anomalies,
like grains of the paper and smudges and the like.
Glenn
----- Original Message -----
From: "Tony Baechler" <tony@baechler.net>
To: <speakup@linux-speakup.org>
Sent: Friday, November 06, 2015 4:30 AM
Subject: Re: Scanning
According to Project Gutenberg Distributed Proofreaders (pgdp.net if you're
interested), they actually recommend not scanning at 600 DPI. They
recommend 300 DPI for most books and 400 DPI in rare cases. I can confirm
this to be the case in my experience. When I scan at the highest
resolution, I actually get worse text results. Not only does 300 DPI scan
faster, but seems to do a better job. Of course I don't know about
non-English text. Maybe 400 DPI works better for other languages.
On 11/5/2015 7:30 AM, John G Heim wrote:
> I did a lot of experimentation while scanning in the D&D manual. I found
> that I got best text recognition when I scanned in the page as line art.
> My
> scanner has a top resolution of 600 dots per inch. I don't know if that's
> good or bad. It's is a really ancient scanner. Someone just gave it to me
> because they were upgrading to Windows XP and it didn't have drivers. When
> would that have been, 2001? But it still works great in linux.
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Scanning Cheryl Homiak
` Scanning Chris Brannon
` Scanning Cheryl Homiak
` Scanning John G Heim
` Scanning Jude DaShiell
` Scanning Tony Baechler
` Scanning Willem van der Walt
` Glenn [this message]
` Scanning Chris Brannon
` Scanning Cheryl Homiak
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=FCA4A842C8784E97A3FCCCF581070EAD@LennyAcer5720 \
--to=glennervin@cableone.net \
--cc=speakup@linux-speakup.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).