From: Christopher Moore <christopher.h.moore@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: changing synths
Date: Sat, 30 May 2009 20:48:58 -0400 [thread overview]
Message-ID: <20090531004858.GA6316@arch> (raw)
In-Reply-To: <20090530083503.GA25793@rx.localhost>
Hello,
I was all set to run Chuck's talkwith script but it wasn't necessary.
I had speakup running with espeakup.
Next I loaded the dectlk module and specified a serial port lite this:
sudo modprobe speakup_dectlk ser=1
Speakup read out some dectalk commands and finished with dectalk
expressed detected.
Next I unloaded espeakup like this:
sudo /etc/rc.d/espeakup stop
And speakup automatically switched to the dectalk with having to do
anything else. I also verified that the synth parameter contains
dectlk.
I guess I have two questions for Chuck. First, why two scripts? Do
they do different things?
And, second, now that speakup seems to be smart enough to switch to the
hardware synth when the soft connector is killed, when are these scripts
necessary?
You may want to include a README file in the tarball to explain some of
this stuff.
FYI, I'm running arch linux with sudo installed. I expect we'd get
similar behavior on a debian based system.
Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Christopher Moore
` Gregory Nowak
` Chuck Hallenbeck
` Christopher Moore [this message]
` Chuck Hallenbeck
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=20090531004858.GA6316@arch \
--to=christopher.h.moore@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).