andrewlylegould at gmail.com
Thu Jan 29 07:09:56 PST 2009
On Thu, Jan 29, 2009 at 7:11 AM, Reko Turja <reko.turja at liukuma.net> wrote:
> From: "Gary Kline" <kline at thought.org>
> Sent: Thursday, January 29, 2009 4:23 AM
> To: "Andrew Gould" <andrewlylegould at gmail.com>
> Cc: "Reko Turja" <reko.turja at liukuma.net>; "FreeBSD Mailing List" <
> freebsd-questions at freebsd.org>
> Subject: Re: OCR...
> On Wed, Jan 28, 2009 at 07:33:41PM -0600, Andrew Gould wrote:
>>> On Wed, Jan 28, 2009 at 5:09 PM, Gary Kline <kline at thought.org> wrote:
>>> > On Wed, Jan 28, 2009 at 01:32:57PM -0600, Andrew Gould wrote:
>>> > > On Wed, Jan 28, 2009 at 1:22 PM, Gary Kline <kline at thought.org> > >
> > > > well, damage is probably done. how can i check the > > >
>>> > > > i tried to increase it by creating huge ppm and tif > > >
>>> files, but
>>> > > > then that's really absurd since there can only be just > > >
>>> so much
>>> > > > data per image. i _could_ try xv and jpeg and > > >
>>> smoothing image
> Yeah, if the image resolution is already at 72DPI, there's sadly no trick
> in the world that can reliably return the "lost" information. I've read some
> horrid scans with low resolution in Finereader, and it can grab much of the
> information nicely. With low resolution be prepared to manually correcting
> problem spots though. Only reliable way to quesstimate resolution is the
> font size when at 100% in the screen. If the text is about 10 pixels high,
> the information has probably been stored in 72DPI for space saving purposes.
> Wasn't aware of the FreeBSD/Linux backend, but if that works it'd be great
> - haven't myself visited their website in ages as the version I have does
> the job I got it for.
I may have used the wrong term. I think it used to be an sdk; but now
there's a product with "extended platform support" for Linux and FreeBSD.
More information about the freebsd-questions