- From: Young, Milan <Milan.Young@nuance.com>
- Date: Mon, 11 Jun 2012 17:29:08 +0000
- To: Hans Wennborg <hwennborg@google.com>, Dominic Mazzoni <dmazzoni@google.com>
- CC: "public-speech-api@w3.org" <public-speech-api@w3.org>, Adam Sobieski <adamsobieski@hotmail.com>, Glen Shires <gshires@google.com>
While I agree with Dominic's arguments, I doubt the subtle difference in semantics between recognition/recognizer or synthesis/synthesizer would be appreciated by developers. My vote is for the original synthesizer/recognizer combo because the words pair well together. -----Original Message----- From: Hans Wennborg [mailto:hwennborg@google.com] Sent: Monday, June 11, 2012 10:08 AM To: Dominic Mazzoni Cc: public-speech-api@w3.org; Adam Sobieski; Glen Shires Subject: Re: Rename "TTS" object to "TextToSpeech" On Mon, Jun 11, 2012 at 5:42 PM, Dominic Mazzoni <dmazzoni@google.com> wrote: > How about SpeechRecognition and SpeechSynthesis instead of > SpeechRecognizer and SpeechSynthesizer? > > The reason being that the APIs are really interfaces to control and > dispatch speech recognition and synthesis at a high level, the actual > recognizer and synthesizer are not necessarily local (though they > could be), they may be in a different process or on a remote server. That's a good argument. I'm happy with SpeechRecognition and SpeechSynthesis if others agree. Thanks, Hans
Received on Monday, 11 June 2012 17:29:37 UTC