Re: [g-a-devel]gnome-speech ...
- From: Marc Mulcahy <marc mulcahy sun com>
- To: Michael Meeks <michael ximian com>
- Cc: accessibility mailing list <gnome-accessibility-devel gnome org>
- Subject: Re: [g-a-devel]gnome-speech ...
- Date: Mon, 19 Aug 2002 14:35:37 -0600
Hi Michael,
Yes, this is definitely true. I'm in the middle of implementing new
gnome-speech API on a branch and have decided to not do any driver
implmentation work on the old branch. If this work seems trivial, then
maybe its worth doing anyway.
Marc
At 10:42 AM 8/19/2002 +0100, Michael Meeks wrote:
Hi Marc,
Just poked at gnome-speech and it seems that the festival module,
simply pokes at the known port for festival, but doesn't try to activate
the server when it starts up.
I appreciate there may be acute lifecycle issues with that; so it's
prolly best to pick a random (user) port, and fork festival_server
assigned to that port [ repeat if it fails to bind ], and talk to that
port - instead of to 1314. Then you at least have the liberty of killing
the thing as you exit [ that is if you have that degree of lifecycle
control yet ]
Either way - it seems far better for gnome-speech to activate it than
simply failing silently when it can't find it.
Regards,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
_______________________________________________
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]