On Fri, 28 Mar 2008 17:42:24 +0000, Rob Kendrick <[EMAIL PROTECTED]> wrote: > On Fri, 2008-03-28 at 19:24 +0100, Goundy wrote: > >> This is my proposal for the Page reader GSoC idea. >> I've done a little search to try getting something portable and >> powerful, I found some interesting TTS engines like: >> speech dispatcher (http://www.freebsoft.org/speechd): provides a >> powerful device independant C Api to write TTS applications. >> Gnome-speech library: This could be the best choice but the only problem >> is that it may be not portable. >> There's some other engines, and the choice need a study and some >> feedbacks from the netsurf team > > The way I thought this should be done is to abstract speech synthesis > APIs ourselves, in much the same way we abstract the plotting. ie, make > the core call certain calls that the front end must implement for doing > speech. This enables lightweight use of a systems's local or built-in > speech without bringing in any dependencies. > > (So, under Windows it would call SAPI, under RISC OS it would call > eSpeak, and under Linux perhaps it could call libfestival?)
For what it's worth (I suspect not a great deal :)) I agree with Rob here. It's as beneficial to have a generic way of talking to a TTS engine as we currently have for presenting content in a visual medium. This supports our portability goal. J.
