From: "Kristoffer Gustafsson" <kg84@dreamwld.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: status of speakup support for espeak
Date: Fri, 11 Jul 2008 23:09:37 +0200 [thread overview]
Message-ID: <003701c8e39a$6d8ac9a0$0900a8c0@evelina> (raw)
In-Reply-To: <97159008-427e-4aef-9a24-39f80fead43b@default>
Hello!
I compiled mine myself, but there should be rpms for speech dispatcher, at
least.
speechd-up I don't really remember how I did with that, but I think that I
compiled that one.
For information about speech synthesizer settings and how to set tem up,
look in the speechd.conf file that is the configuration for speech
dispatcher. there are examples for festival, and for the dec talk speech
synthesizer from fonix as well.
don't forget that you need to set up festival as a server with the
festival --server command if you want to use it with speech-dispatcher and
speechd-up.
if you want the rpms, try searching on rpmfind.net for speech-dispatcher and
speechd-up.
I can see too if I have some rpms too, I can have some in my linux folder.
Hope this helps, if you need more help, just ask for it.
/Kristoffer
----- Original Message -----
From: <DON.RAIKES@ORACLE.COM>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, July 11, 2008 10:50 PM
Subject: RE: status of speakup support for espeak
> Kristopher,
>
> That would be great!
>
> Is there an rpm for speech-dispatcher that I should use to start the
> process, or do I have to compile it from scratch?
>
> Any configuration / setup info would be greatly appreciated.
>
> -----Original Message-----
> From: Kristoffer Gustafsson [mailto:kg84@dreamwld.com]
> Sent: Friday, July 11, 2008 1:21 PM
> To: Speakup is a screen review system for Linux.
> Subject: Re: status of speakup support for espeak
>
>
> Hello
> You don't need to use espeak at all, speech-dispatcher has support for
> festival that works very will with speakup and the softsynth support for
> speech-dispatcher.
> I've tried it myself.
> I can help you with this if you want.
> /Kristoffer
> ----- Original Message -----
> From: <DON.RAIKES@ORACLE.COM>
> To: "Speakup-List (E-mail)" <Speakup@braille.uwo.ca>
> Sent: Friday, July 11, 2008 8:15 PM
> Subject: status of speakup support for espeak
>
>
>> Hi all,
>>
>> Are there plans to make speakup software synth work with the espeak
>> synthesizer, or has it already been implemented?
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> _______________________________________________
> 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: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
DON.RAIKES
` Samuel Thibault
` DON.RAIKES
` Samuel Thibault
` William F. Acker WB2FLW +1-303-722-7209
` Kristoffer Gustafsson
` DON.RAIKES
` Kristoffer Gustafsson [this message]
` Steve Holmes
Hynek Hanke
` Kerry Hoath
` John Heim
` Hynek Hanke
` Willem van der Walt
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='003701c8e39a$6d8ac9a0$0900a8c0@evelina' \
--to=kg84@dreamwld.com \
--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).