- From: Stephane Boyera <boyera@w3.org>
- Date: Mon, 30 Jun 2008 19:39:58 +0200
- To: Janusz Lukasiak <janusz@eumx.net>
- Cc: public-mw4d@w3.org
> I mentioned the same technique (text-to-voice) because I think I could > beneficial to both groups. yes exactly. > How all that (text-to-voice and voice-to-text) is to be included in a cheap > mobile phone isn't obvious :-( this need to be explored further. I believe that TTS (text to speech) can be at different locations in the delivery chain. in the classical Voice architecture (i mean W3C voice architecture, related to VoiceXML), the "browser" is the voice server receiving people's calls (i.e. not on the phone, but at the other end) however, in modern phone, there are also TTS on the phone itself. So concerning voice rendering, the availability on phone is not a key factor imho, like it is for e.g. a browser for mobile browsing. That said, voice has also clear limitations imho: culturally irrelevant in lots of cultures, high required expertise to develop voice applications, expensive infrastructure for good TTS and VR engines (voice recognition), lack of language support,... I believe that we can still aim at providing visual content that could be understandable by people not being able to read or write, through iconic languages. Stephane -- Stephane Boyera stephane@w3.org W3C +33 (0) 4 92 38 78 34 BP 93 fax: +33 (0) 4 92 38 78 22 F-06902 Sophia Antipolis Cedex, France
Received on Monday, 30 June 2008 17:40:15 UTC