From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: can't get espeak working with speech dispatcher and speechd-up
Date: Tue, 22 Aug 2006 13:37:24 -0700 [thread overview]
Message-ID: <20060822203724.GA32349@localhost.localdomain> (raw)
In-Reply-To: <20060822190208.GA12565@hhs48.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thanks to Tyler S., Hynek, and Chuck in no particular order for your
help.
When installing espeak, I just copied the espeak-data directory
verbatim to /usr/share/, without checking the permissions on the
directory or files, assuming they were ok. When testing espeak, I
tested it as root, without bothering to check if a normal user could
use it also. It turns out that when running espeak as a normal user,
it couldn't access the files in /usr/share/espeak-data, and fixing the
permissions solved this, and also allowed espeak to be useable with
speechd-up. So, that was the problem, which I admit I should have
thought of sooner.
Also, Chuck was right that the speak binary has to exist in /usr/bin,
rather then in /usr/local/bin, however, since I don't like software
installed manually to exist outside of /usr/local/, providing the full
path to speak in espeak-generic.conf solves that issue, while still
allowing speak to remain in /usr/local/bin. Speaking of that, is it
possible to specify the path to espeak-data without having to
recompile? If not, where in the source can this be changed? I'd like
to have espeak-data in /usr/local/share, rather then in /usr/share.
I'm writing this message on the machine which I've installed espeak
on, and have to side with all the other comments I've seen on this
list. The speech quality is very refreshing when compared to festival,
flite, and even to the bns. My hat off to Jonathan for such a
great software synth, with a small footprint, that sill has lots of potential down the road.
Greg
On Tue, Aug 22, 2006 at 03:02:08PM -0400, chuckh@hhs48.com wrote:
> Greg,
>
> I just configured a system similarly with no problems. Did you perchance
> put the speak command in /usr/local/bin instead of /usr/bin? Typing the
> speak command on a command line would work either way, but I think
> speech-dispatcher wants it to be in /usr/bin.
>
> --
> The Moon is Waning Crescent (1% of Full)
> Only 10 kinds of people: those who do binary, and those who do not.
> But you can get a few downloads from http://www.mhcable.com/~chuckh
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
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.3 (GNU/Linux)
iD8DBQFE62sE7s9z/XlyUyARApWLAKCHKyMj02L+OjEJjHLacBI1j6faoQCggbhH
atnMwVbDSJws/KjUg9Xqows=
=z0Fw
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Tyler Spivey
` Gregory Nowak
` Tyler Spivey
` hanke
` chuckh
` Gregory Nowak [this message]
` Jonathan Duddington
` Gregory Nowak
` Jonathan Duddington
` Gregory Nowak
` Gary Cramblitt
` Jonathan Duddington
` Michael Whapples
` Gary Cramblitt
` Willem van der Walt
` Lorenzo Taylor
` Steve Holmes
` Jonathan Duddington
` gena-j
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=20060822203724.GA32349@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).