SpeechAPI: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 31: Line 31:
*The developer should be able to start, stop, handle errors and multiple requests as required.
*The developer should be able to start, stop, handle errors and multiple requests as required.
<br>
<br>
== 2.Text To Speech API  ==
The text to speech API will be based on google's proposal([http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Feb/att-0022/htmltts-draft.html]).This API can be used for speech translation, turn by turn navigation, dialog systems etc.
==== API Design -  ====
*The API will introduce a new element &lt;tts&gt; that extends HTMLMediaElement. It will be similar to how the &lt;audio&gt; and&nbsp;and &lt;video&gt; tags are implemented.<br>
*A playback UI should allow the user to start, stop and disable text to speech. The current spoken word can be highlighted.<br>
*The developer should be able to specify the language, position, start/stop playback and handle errors programmatically. <br>
*The API should itself be independent of the underlying speech synthesizer. If speech synthesis is not supported, appropriate text should be displayed. <br>
*What speech engines is yet to be decided.
<br>


   <h2>nsSpeechRequest</h2>
   <h2>nsSpeechRequest</h2>
18

edits