Does Speech Dispatcher crash in Karmic when a synthesizer other than Espeak is used? I run Jaunty and find that Espeak will often stop talking when I use Speech Dispatcher. With Flite, these crashes are rare. If I use Gnome-speech with Espeak, Espeak will often interrupt itself but not crash, per-se. May I suggest that either Gnome-speech be included or that Flite be the default voice until the troubles with Espeak and Karmic are addressed?
Best, Dave On Oct 21, 2009, at 9:19 PM, Aruni Sharma wrote: > Hi, do we no longer have the option of using gnome-speech? although > speech-dispatcher has been made the default, it would have been better > if gnome-speech was also available, at least till the time > speech-dispatcher is stable enough. > Thanks, > Aruni. > > On 10/22/2009 3:55 AM, Bill Cox wrote: >> Hi, Luke. >> >> Thanks for working on accessibility. I feel really rotten about >> complaining about the bugs without putting in effort into debugging. >> However, my boss is all over me at the moment to get another project >> back on schedule. I'm sure you know what that's like. >> >> However, over the next year, I promise to find some time to nail a >> bug >> or two, like the crash in speech dispatcher. In the meantime, we >> should probably set expectations for users, and let them know it will >> be a while before Orca is working in a stable manner in the latest >> Ubuntu. It's an unfortunate situation, but blind users are simply >> not >> able to chip in and fix things when accessibility is broken, so it >> will be up to the very few of us interested in accessibility who >> still >> have decent vision to pull it off. >> >> Best regards, >> Bill >> >> On Wed, Oct 21, 2009 at 5:59 PM, Luke Yelavich<[email protected]> >> wrote: >> >>> On Thu, Oct 22, 2009 at 08:46:26AM EST, Bill Cox wrote: >>> >>>> Sorry guys, I know there's some of you out there who actually >>>> work on >>>> Ubuntu accessibility, but the current state sucks. I certainly >>>> hope >>>> Ubuntu decides at some point to make accessibility a priority. >>>> >>> I can understand why, as a user, you feel that way. Unfortunately >>> I am the only one so far as I know of, actively working on >>> improving Ubuntu's accessibility, and while I do as much as I can >>> to make things work as well as they can, I have other matters that >>> I need to attend to, due to working for Canonical and being >>> responsible for other parts of the desktop as well, so I can only >>> do so much in the time I allocate for accessibility work. >>> >>> Unfortunately the speech-dispatcher crasher is at the moment, >>> somewhat beyond my current skills to debug, although learning >>> valgrind will likely help me get better with sed debugging, and >>> hopefully get rid of the speech-dispatcher crash. >>> >>> So if you really want Ubuntu's accessibility to get better, I urge >>> you to consider helping out in whatever way you can, even if its >>> only filing and triaging bugs, thats something. The more bugs that >>> are in a triaged state, the less work I have to do, and the more >>> bugs I can attempt to fix. >>> >>> I hope you all understand, and will do what you can to help. >>> >>> Regards >>> Luke >>> >>> -- >>> Ubuntu-accessibility mailing list >>> [email protected] >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility >>> >>> >> > > -- > Ubuntu-accessibility mailing list > [email protected] > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
