From: Michael Whapples <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: What are the advantages of Speakup over Orca?
Date: Sun, 17 Aug 2008 17:33:17 +0100 [thread overview]
Message-ID: <1218990797.6617.9.camel@localhost> (raw)
In-Reply-To: <48A7EDD7.1020005@baechler.net>
On Sun, 2008-08-17 at 02:22 -0700, Tony Baechler wrote:
> Cody Hurst wrote:
> > Speakup is strictly for command line, a virtual console. Orca on the
> > other hand is intended to be a screen reader for the GUI desktop
> > environment, gnome. If you are good with bash and want to work in the
> > command line without the hastle of a desktop, then using speakup would
> > be the best choice. However I'm sure you know already you will need an
> > external synthisizer such as a double talk lt or a bns. Orca is
> > maintained by sun, speakup is not.
>
>
>
>
> Huh? What about using ESpeak or other software synths? Also, are you
> saying that Speakup is unmaintained? I see commits every few days and
> the bugs which I've reported all got fixed. Granted there is not a
> company developing it, but there aren't very many people testing it
> either. I think your statement that Orca is maintained by Sun and
> Speakup isn't is unfair and misleading.
I would have to agree with what you said (regarding software speech and
who maintains each). The only thing I would say is that orca may appear
more active, but I feel it has more to be sorted out, eg. it still has
times when it can become unresponsive, times when it doesn't seem to
work with applications as you might expect, etc, where as I find speakup
is a very good reliable system I know I can always fall back to and get
speech output from my system. I would say that with software speech yes
there are some extra limitations to using speakup with a hardware synth,
eg. sometimes the software synth or driver software (such as speechd-up
and speech-dispatcher) may stop running, or software speech output isn't
possible for early parts of the boot process, but these situations are
rare that they may occur, or may be required.
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Charlie Dorff
` Tony Baechler
` Cody Hurst
` Tony Baechler
` Michael Whapples [this message]
` Nick Stockton
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=1218990797.6617.9.camel@localhost \
--to=mwhapples@aim.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).