public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "propaine" <propaine@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: triple talk tricks
Date: Wed, 31 May 2006 16:49:48 -0400	[thread overview]
Message-ID: <001701c684f3$c22a4fb0$2f01a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <7.0.1.0.0.20060531131008.01041110@freedomchat.org>

I think the TripleTalk's a little faster.  Also, though as far as I know
there are still no drivers for causing it to speak via USB, it can at least
keep its battery charged via USB.

Propaine
----- Original Message ----- 
From: "ace" <ace@freedomchat.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, May 31, 2006 1:10 PM
Subject: Re: triple talk tricks


> What is the difference between TripleTalk External and DoubleTalk
> LT?  They sound the same (using RCSystems DoubleTalk chip) the
> TripleTalk is just more expensive.
>
>
> At 02:20 PM 5/30/2006, you wrote:
> >Do you mean the internal TripleTalk, in which case I'm sorry I can't
help.
> >I got an external one a few months ago, and only had to connect it to the
> >port where the DoubleTalk LT had been connected; it worked and works
fine.
> >
> >Propaine
> >----- Original Message -----
> >From: "Charles Hallenbeck" <chuckh@hhs48.com>
> >To: "Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
> >Sent: Tuesday, May 30, 2006 1:40 PM
> >Subject: triple talk tricks
> >
> >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Has anyone been able to trick any of the speakup serial drivers into
> > > talking to the triple talk? I'd be curious to know it might be done,
> > > given that there is no proper driver for the device.
> > >
> > > - --
> > > The Moon is Waxing Crescent (13% of Full)
> > > Get downloads from http://www.mhcable.com/~chuckh
> > >   and remember, INFORMATION WANTS TO BE FREE!
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.3 (GNU/Linux)
> > >
> > > iD8DBQFEfIOPXnuiIOyDVQURAmEQAJ9JOOxF/Pa/OCZZbMuCWNB8xX68DACdHje/
> > > xLhu3uMBAZgagA3WLuzwpI8=
> > > =KzWx
> > > -----END PGP SIGNATURE-----
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > >
> > > --
> > > No virus found in this incoming message.
> > > Checked by AVG Free Edition.
> > > Version: 7.1.394 / Virus Database: 268.7.4/351 - Release Date:
5/29/2006
> > >
> > >
> >
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.8.0/352 - Release Date: 5/30/2006
>
>



  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Charles Hallenbeck
 ` propaine
   ` Charles Hallenbeck
     ` John Heim
     ` Kirk Reiser
   ` ace
     ` propaine [this message]
     ` Joseph C. Lininger

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='001701c684f3$c22a4fb0$2f01a8c0@ALBERTLC7SN0ZA' \
    --to=propaine@verizon.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).