From: wlestes@hamlet.uncg.edu
To: blinux-list@redhat.com
Subject: [akuchlin@cnri.reston.va.us: [ocr] Where are we?]
Date: Sat, 13 Jun 1998 15:49:09 -0400 [thread overview]
Message-ID: <199806131949.PAA01054@duvallp.uncg.edu> (raw)
OCR under linux
------- Start of forwarded message -------
Return-Path: <akuchlin@cnri.reston.va.us>
From: Andrew Kuchling <akuchlin@cnri.reston.va.us>
Date: Thu, 14 May 1998 14:50:37 -0400 (EDT)
To: ocr@icemark.ch
Subject: [ocr] Where are we?
In-Reply-To: <199805141836.OAA02811@duvallp.uncg.edu>
Sender: owner-ocr@icemark.ch
Precedence: bulk
Reply-To: ocr@icemark.ch
wlestes@hamlet.uncg.edu writes:
>After joining and queerying majordomo, I find nothing on the current
>of ocr under linux. So, where are? Are there urls, ftp sites, etc. to
>look at?
The current state of things is that Stuart Inglis has a GPL'ed
OCR engine called SOCR. However, there's no GUI interface to it.
Various people have suggested writing a GUI using Qt or GTk or some
other toolkit, but I don't know if anyone's started working on such a
thing. Anyone?
It would be great if there was a crude prototype using GTk
ready in time for the Linux Expo on May 28.
List archive:
<URL:http://www.findmail.com/listsaver/ocr/>
SOCR page:
<URL:http://www.cs.waikato.ac.nz/~singlis/ocr/>
- --
A.M. Kuchling http://starship.skyport.net/crew/amk/
Numbers and lines have many charms, unseen by vulgar eyes, and only discovered
to the unwearied and respectful sons of Art. In features the serpentine line
(who starts not at the name) produces beauty and love; and in numbers, high
powers, and humble roots, give soft delight.
-- E. De Joncourt
- -
Subscribing: send "subscribe ocr" in a message body to majordomo@icemark.ch
Unsubscribing: send "unsubscribe ocr" in a message body to majordomo@icemark.ch
------- End of forwarded message -------
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199806131949.PAA01054@duvallp.uncg.edu \
--to=wlestes@hamlet.uncg.edu \
--cc=blinux-list@redhat.com \
/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).