From: Hynek Hanke <hanke@brailcom.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Espeak Problems
Date: Tue, 27 Feb 2007 20:34:29 +0100 [thread overview]
Message-ID: <1172604869.7608.3.camel@chopin> (raw)
In-Reply-To: <BAY102-DAV5CCA65F8D2604C4F1E4688F820@phx.gbl>
On Tue, 2007-02-27 at 11:23 -0800, Zachary Kline wrote:
> I've begun trying to configure Espeak and Speech Dispatcher. Unfortunately, despite commenting the flite lines in the configuration file, I still get Flite output. Is this something obvious I'm missing?
Hello,
did you set DefaultModule to espeak-generic
DefaultModule espeak-generic
(without any # sign) and commented out the LanguageDefaultModule
options (put the # sign before them)?
If yes, please send me your speechd.conf configuration file.
Have a nice day,
Hynek
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Hynek Hanke [this message]
` Zachary Kline
` Hynek Hanke
` Steve Holmes
` Hynek Hanke
` 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=1172604869.7608.3.camel@chopin \
--to=hanke@brailcom.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).