public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "kevin" <kjsisco@rcn.com>
To: <speakup@braille.uwo.ca>
Subject: Re: speakup question?
Date: Mon, 13 Oct 2003 14:27:08 -0400	[thread overview]
Message-ID: <000d01c391b7$9d4d08e0$7f4cfea9@Kevin> (raw)
In-Reply-To: <20031013173950.GC1779@lnx3.holmesgrown.com>

ah I see.  And would any special configurations have to be made or would it
recognize any external device automaticly.  It looks like it would have to
be manually configured, but I could be wrong.
Kevin
email:
kjsisco@rcn.com

----- Original Message ----- 
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, October 13, 2003 1:39 PM
Subject: Re: speakup question?


> At the present time, hardware speech is the only way to go.  That
> would include internal synthesisers like the double talk or Accent PC
> plus the usual array of exter serial synths.  Don't think they ever
> got the JTripple talk to go though.
>
> On Mon, Oct 13, 2003 at 01:29:56PM -0400, kevin wrote:
> > Hello I have a question about the speakup project.  I am verry familear
with the alsa drivers because I helped with the release of 9.1, but I am
unclear on some things.  Does the screen reader use it's own internal
synthesizer?  Does one have to be attached?  I was not informed on this
point.
> > Kevin
> > email:
> > kjsisco@rcn.com
>
> -- 
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
>
> _______________________________________________
> 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
 kevin
 ` Steve Holmes
   ` kevin [this message]
     ` Janina Sajka

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='000d01c391b7$9d4d08e0$7f4cfea9@Kevin' \
    --to=kjsisco@rcn.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).