public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas D. Ward" <tward1978@earthlink.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Linux with speech: which way to go?
Date: Mon, 5 May 2003 13:20:55 -0400	[thread overview]
Message-ID: <000e01c3132a$b0ed4600$e1859641@tward1978> (raw)
In-Reply-To: <000401c31320$20b945c0$e4a2f7a5@wright>

Hi, when software speech is an issue I would also suggest looking at yasr.
I've been playing with it on my laptop, and I really like the screen reader.
I've got it working with flite and also Viavoice, and it is a pretty nice
screen reader.
You can get the yasr source from:
yasr.sourceforge.net

----- Original Message -----
From: Beth Wright <beth.wright@mindspring.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, May 05, 2003 12:02 PM
Subject: Linux with speech: which way to go?


> Hi.  I'm just starting to learn about Linux, and am wondering which speech
> package (if that's the right word) I should choose, EmacSpeak or SpeakUp.
> From what little I can understand, I gather that the folks on this list
much
> prefer SpeakUp, but like to have EmacSpeak around as sort of a backup.  My
> problem is that I only have software speech on my PC, and apparently won't
> work with SpeakUp.  I don't have Linux installed yet and, before I get
> someone over here to help me, I'd like to be in a position to give them a
> few suggestions on how to proceed.  I'd sure appreciate any pointers I can
> get from some of you more experienced users.
>
> Beth Wright
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



      parent reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Beth Wright
 ` Alexandre Alves Tôco
 ` Thomas D. Ward [this message]

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='000e01c3132a$b0ed4600$e1859641@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).