-----BEGIN PGP SIGNED MESSAGE-----
Speechd-up is still the way to link software speech to speakup.
Just do an emerge speechd-up to install the packages. The default
synthesizer is espeak, and it and speech dispatcher will be installed as
dependencies of speechd-up. Once you have everything emerged, add
speech-dispatcher and speechd-up to your default runlevel.
Yes, the files that were in /proc/speakup have been moved to
I will also look into modifying the speakup ebuild to install
On Thu, Apr 24, 2008 at 03:07:57PM +1200, Robert Grieve wrote:
> Thanks for the great new packge.
> Owing to the amount of change in how this is set up,
> I wonder if some docs need to be more actively published.
> How much chance is there of altering the ebuild so we get some of the
> documentation that used to live under /usr/linux/Documentation/speakup
> under /usr/share/doc/speakup-3.X?
> ???As far as the sftsyn situation I was asking about I have 3 further
> To get software synthesis working, we need a synthesizer (like
> festival,flite,or espeak), and we need a way to configure all the params
> (like rates). 2 things used to be done for this. One was the files which
> used to live under /proc/speakup, the other was a complex mesh of
> synth,speech-dispatcher, synth specific configs, and speechd-up.
> i) I take it speechd-up is now dead and buried? Replaced by 'start=1'
> ii) I take it that the config files for rates etc now live in sysfs
> iii) What services would you recommend adding to what runlevels for the
> userspace software synth? I'm currently assuming that espeak plus
> speech-dispatcher should about do it, and that the
> speech-dispatcher config still has meaning. Thoughts?
> Thanks much
gentoo accessibility team lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
-----END PGP SIGNATURE-----
email@example.com mailing list