1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Hi Robert, |
5 |
|
6 |
Speechd-up is still the way to link software speech to speakup. |
7 |
Just do an emerge speechd-up to install the packages. The default |
8 |
synthesizer is espeak, and it and speech dispatcher will be installed as |
9 |
dependencies of speechd-up. Once you have everything emerged, add |
10 |
speech-dispatcher and speechd-up to your default runlevel. |
11 |
|
12 |
Yes, the files that were in /proc/speakup have been moved to |
13 |
/sys/module/speakup/parameters. |
14 |
|
15 |
I will also look into modifying the speakup ebuild to install |
16 |
documentation. |
17 |
|
18 |
|
19 |
On Thu, Apr 24, 2008 at 03:07:57PM +1200, Robert Grieve wrote: |
20 |
> Thanks for the great new packge. |
21 |
> |
22 |
> Owing to the amount of change in how this is set up, |
23 |
> I wonder if some docs need to be more actively published. |
24 |
> How much chance is there of altering the ebuild so we get some of the |
25 |
> documentation that used to live under /usr/linux/Documentation/speakup |
26 |
> under /usr/share/doc/speakup-3.X? |
27 |
> |
28 |
> ???As far as the sftsyn situation I was asking about I have 3 further |
29 |
> questions. |
30 |
> |
31 |
> To get software synthesis working, we need a synthesizer (like |
32 |
> festival,flite,or espeak), and we need a way to configure all the params |
33 |
> (like rates). 2 things used to be done for this. One was the files which |
34 |
> used to live under /proc/speakup, the other was a complex mesh of |
35 |
> synth,speech-dispatcher, synth specific configs, and speechd-up. |
36 |
> |
37 |
> i) I take it speechd-up is now dead and buried? Replaced by 'start=1' |
38 |
> ii) I take it that the config files for rates etc now live in sysfs |
39 |
> somewhere. |
40 |
> iii) What services would you recommend adding to what runlevels for the |
41 |
> userspace software synth? I'm currently assuming that espeak plus |
42 |
> speech-dispatcher should about do it, and that the |
43 |
> speech-dispatcher config still has meaning. Thoughts? |
44 |
> |
45 |
> Thanks much |
46 |
> Robert |
47 |
|
48 |
|
49 |
|
50 |
- -- |
51 |
William Hubbs |
52 |
gentoo accessibility team lead |
53 |
williamh@g.o |
54 |
-----BEGIN PGP SIGNATURE----- |
55 |
Version: GnuPG v2.0.9 (GNU/Linux) |
56 |
|
57 |
iEYEARECAAYFAkgQD4kACgkQblQW9DDEZTiZdQCgmx+N1EodSh5MrAOOlvPMbnyO |
58 |
jrIAoLIBJikcVxCWdjPT07nQNPbHVDKG |
59 |
=s5IG |
60 |
-----END PGP SIGNATURE----- |
61 |
-- |
62 |
gentoo-accessibility@l.g.o mailing list |