From: nick G <nick6489@optonline.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: bug in Speakup-utils
Date: Fri, 28 May 2004 08:53:32 -0400 [thread overview]
Message-ID: <003d01c444b2$c824aa10$cc00a8c0@nickysp4> (raw)
In-Reply-To: <20040528004554.GA2385@lnx3.holmesgrown.com>
It isn't moot, I'll say that much. I liked speakup config, easy easy
interfase. This looks similar, and should be included in speakup 2.00.
Thanks,
Nick
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 27, 2004 8:46 PM
Subject: Re: bug in Speakup-utils
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I would say that speakuputils is just about a moot point now. The
> latest CVS versions of Speakup have additional keys for changing
> pitch, rate and volume. from the console now. Just use speakup-1 thru
> speakup-6 to change them. <Hmmm> no tone or voice here. Any way,
> we're close. The speakupconf script that can be found in
> /usr/src/linux/drivers/char/speakup can save and restore speech
> settings and is sensative to which synth is being used at the time.
>
> On Wed, May 26, 2004 at 09:52:34PM -0500, Adam Myrow wrote:
> > Apparently, Speakup Utils has problems if the exact settings it expects
> > aren't present. For example, with the Accent PC, there is no voice
> > setting, but instead, there is a tone setting. So, when you arrow to
the
> > voice setting, a value of 0 is reported. After this, all values are
stuck
> > at zero and cannot be changed. It would seem to me that the logical
> > approach would be to skip non-existent settings. Another approach would
> > be to make all synthesizers in Speakup have the same controls. I.E.
give
> > the Accent drivers a voice setting and have it map to the tone setting.
> > This is basically what screen readers for that other OS tend to do.
> > Which approach seems more logical to you all?
>
> - --
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFAtovCWSjv55S0LfERAnxnAJ418g7rPwJ8OKXxFkVr0fJpWeo0jgCfXswT
> OLFFH5X3hzH/axYadcL3hUg=
> =lpWY
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Myrow
` Steve Holmes
` nick G [this message]
` Steve Holmes
` Adam Myrow
` nick G
` Steve Holmes
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='003d01c444b2$c824aa10$cc00a8c0@nickysp4' \
--to=nick6489@optonline.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).