-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 In reply to my original message, I figured out my problem I just reported. Since I use a RAMFS I had to do a 'update-initramfs -u' and that got me to use the correct speakup modules. It appears that most of the speakup parameters are updating with speakupconf load now. I still make a couple observations but I will have to trace the script and see if I can offer more details. But at least I don't get a bunch of errors like I did previously. But I just tried to restore an updated characters from my saved parameters and that doesn't work. I can save individual chars like '122 z' and that seemed to update correctly with a kernel message that one character was replaced. So I may have to rethink how speakupconf will work. Hmmm, maybe a rewrite is in order. On Sun, Mar 15, 2009 at 11:38:34AM -0700, Steve Holmes wrote: > I'm not sure what is goin on here but I tried successfully to build > speakup from git and did a 'make modules_install' from root and all > modules were built and installed in the ..../extra/speakup and show > today's date. > > But when I try and update /sys/module/speakup/parameters/characters to > get rid of that zehd crap, I get the following error. > > [ 957.339003] character descriptions reset to defaults > and the update does not take place. I get this when I edit the file > directly and attempt to save it. If I echo the updated file from > another location, to the proper place, I get no messages but it > doesn't get updated. > > Also, I do not see a file called direct anywhere in the > /sys/module/speakup/parameters direct any place. This makes me wonder > if I even got the right code updated. I can't really tell for sure. > When I do a cat version, > > I see 3.0.3 with software synthesizer driver 2.4. > > Also, when I do a speakupconf load, I still get all the 'invalid > parameter' errors and my punct_* files get emptied. > > On Sun, Mar 01, 2009 at 03:39:23PM -0600, William Hubbs wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Fri, Feb 27, 2009 at 10:55:31AM +0000, Jonathan Duddington wrote: > > > On 27 Feb, Chris Brannon <cmbrannon at cox.net> wrote: > > > > When you type z or read z with the speakup cursor, speakup sends the > > > > text zehd to espeakup. > > > > > > Why not just send "z" ? > > > > Actually this can be done if you are running the latest speakup, it is > > just not set as the default. > > > > There is a sys file for speakup called > > /sys/module/speakup/parameters/direct. If you set the value in there > > to 1, text will be sent directly to espeak with no speakup processing. > > > > William > > > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v2.0.9 (GNU/Linux) > > > > iEYEARECAAYFAkmrAIsACgkQblQW9DDEZThbeACbB0Z+hEIJJ7sDJIPvRZA1tHS0 > > MwMAnRtPIwA8IuuzRnC+cYHHLmmIeDol > > =sxyi > > -----END PGP SIGNATURE----- > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkm9V2gACgkQWSjv55S0LfESIACfYJgd1BMQliwFAG+s6KAvuP8q pKIAoKV1cVXY5mFFOxPlZwOhSlcY7SZz =VK16 -----END PGP SIGNATURE-----
