public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: want to pay bills online in Linux
Date: Wed, 2 Apr 2003 18:55:37 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0304021855001.27155-100000@igueths> (raw)
In-Reply-To: <Pine.LNX.4.53.0304021729000.1092@homerun.midsouth.rr.com>

Speaking of ocr, does anyone know how good jocr is? I am planning on
tinkering with it once I get a scanner, however I just wanted to get some
feedback regarding its usability. I know its command line, but has anyone
here used it and likes it?

May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.

On Wed, 2 Apr 2003, Adam Myrow wrote:

> If you ever figure out a way to do that sort of stuff in Linux, I sure
> hope you post it.  The unfortunate truth is that many sites are so
> hard-coded to expect Internet Explorer or Netscape, that anything else is
> considered inferior.  You can thank Microsoft for including IE with the
> OS and thus making sure everybody who sets up web pages tests with IE and
> nothing else.  There are four things I'd like to do with Linux that would
> make me be able to comfortably use it as my sole OS.  1: print out checks
> to my printer and keep track of finances.  2: print envelopes.  3: have a
> decent OCR package that is at a reasonable price.  4: have the ability to
> create nicely formatted documents and preview them before printing.  Some
> of this is certainly possible already.  I could eventually sit down and
> learn tex or SGML, but a lot of newbies will be a little stubborn about
> learning this.  For me, it's mainly a lack of time.  I have heard of a few
> good commercial OCR packages on this list and intend to investigate them.
> The only free one I am aware of is gocr, and it is far from usable.  I
> wish I knew more about OCR so perhaps I could help make it better.  I know
> that there are a few financial packages out there, but I don't know of any
> which can print checks.  Sorry about the rambling, but I feel for you and
> others who wish we could truly have a choice in OS.  I think things will
> get better when an X screen reader gets to a point of being functional,
> but it looks like that is easier said than done.  It's a shame too.  Linux
> is stable, fairly secure, and even if an application bombs, it doesn't
> take down the whole OS.  I can count on my fingers the number of times
> I've had to reboot a Linux box due to a crash, and all the times it
> happened were when I was testing something which was known to be
> problematic.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Lorenzo Prince
 ` Adam Myrow
   ` Igor Gueths [this message]
   ` Hugh Esco

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=Pine.LNX.4.44.0304021855001.27155-100000@igueths \
    --to=igueths@attbi.com \
    --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).