From: "Thomas D. Ward" <tward1978@earthlink.net>
To: <speakup@braille.uwo.ca>
Subject: Re: This sucks! OCR in Linux
Date: Sat, 12 Apr 2003 15:11:49 -0400 [thread overview]
Message-ID: <005801c30127$5f527e60$77859641@tward1978> (raw)
In-Reply-To: <20030412135855.GA13403@potpal>
I personally don't mind paying for a product if it is a quality product.
After all not every programmer can be expected to work free.
As for OCR there are many good engines floating around such as Fine Reader,
Care MTX, etc, but they are not free. Either you can purchase them, sign a
NDA, and release a closed source OCR app, or you can start from scratch and
take the 4 or 5 years it would take to hopefully get the quality of the pro
grade OCR applications.
Once you recognize time and costs of developing an OCR app a good open
source OCR project would be a huge undertaking without a single return.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
This sucks! Adam Myrow
` Thomas D. Ward
` Igor Gueths
` Lorenzo Prince
` This sucks! OCR in Linux Kenny Hitt
` Thomas D. Ward [this message]
` Buddy Brannan
` Thomas D. Ward
` Adam Myrow
` Kenny Hitt
` Lorenzo Prince
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='005801c30127$5f527e60$77859641@tward1978' \
--to=tward1978@earthlink.net \
--cc=speakup@braille.uwo.ca \
/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).