public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: Re: dectalk or double talk advice
Date: Fri, 22 Jun 2007 12:47:33 -0700	[thread overview]
Message-ID: <20070622194733.GA30841@localhost.localdomain> (raw)
In-Reply-To: <000b01c7b49e$31cd2970$6c01a8c0@tdsportable>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

First, the operating systems mentioned were suse linux, and
netware. There was no mention of windows, thus I don't see how the
reference to jaws fits in, unless it was to explain how jaws gets its
data, which is besides the point.

Also, the reference to usb being the better choice was
inappropriate, since speakup currently doesn't support usb synths, as has
been mentioned here frequently, especially in recent threads. Having
said that, if you're going to rely on speakup, you will want to be
sure that all the work stations you're going to use have at least 1
rs232 serial port. If they don't, then you're in trouble if you
expect to use speakup.

Also, be aware that suse doesn't include speakup in their
distribution, and I'm not aware of any existing suse kernels with
speakup patched into them. You mentioned also not being sure about the
accessibility of slackware. Actually, slackware was the first
distribution to include a speakup-patched kernel in the official
slackware media.

As for which synth to choose, I think the 2 biggest factors in that
decision are the speech, and the price of each. The doubletalk lt is
cheaper than the dectalk usb, which does also have a serial port as
far as I know. As for the speech, I personally prefer that of the
doubletalk, but that's probably because I've used a doubletalk far
more than I have used a dectalk, and others may disagree here as
well. Speech is a very qualitative subject, and there is no synth that
fits every person's taste perfectly. As an aside, you wouldn't have
been able to use a doubletalk pc anyway, because they aren't being produced
anymore, and because it is very hard these days to find a pc with an
isa slot. Hth.

Greg



On Fri, Jun 22, 2007 at 12:23:06AM -0700, Littlefield, tyler wrote:
> First, you're not going to get speech support without a program.
> The screen reader puts hooks in the kernel, or catches the video in the case 
> of jaws, and translates.
> Next, I'd recommend USB, because, if you start using newer systems, most 
> don't have a serial port.
> Third, the accessibility of slackware is fine, unless you insist on running 
> under gnome, x, or something else, then you're really not getting the 
> benafit of linux.
> HTH,


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGfCdV7s9z/XlyUyARAhQoAKC2pAxtaBHQFbcRxJ7X3YAKxDtHqwCg1nOM
uSZ2tei1eRwXa/lpYrCpqgg=
=UAdR
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cody Hurst
 ` Littlefield, tyler
   ` Gregory Nowak [this message]
     ` Cody Hurst
       ` Alex Snow
         ` Cody Hurst
       ` Gregory Nowak
         ` Cody Hurst
           ` Gregory Nowak

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=20070622194733.GA30841@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --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).