W3C home > Mailing lists > Public > public-speech-api@w3.org > May 2012

Re: Rename "TTS" object to "TextToSpeech"

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 15 May 2012 12:49:59 -0700
Message-ID: <4FB2B367.5030905@jumis.com>
To: Dominic Mazzoni <dmazzoni@google.com>
CC: Adam Sobieski <adamsobieski@hotmail.com>, Glen Shires <gshires@google.com>, public-speech-api-contrib-request@w3.org, public-speech-api@w3.org
I second this.

Replace Recognition and Synthesis with the Input and Output.

1. Simple spelling from basic English makes for a broad API like this; 
it's much easier on authors.
2. Speech output may go to an on screen display, not just a speech 
synthesizer.



On 5/15/2012 12:12 PM, Dominic Mazzoni wrote:
> Or, how about renaming both the recognition and TTS parts to make them 
> more consistent: SpeechInput and SpeechOutput.
>
> On Tue, May 15, 2012 at 10:45 AM, Adam Sobieski 
> <adamsobieski@hotmail.com <mailto:adamsobieski@hotmail.com>> wrote:
>
>     Glen,
>
>     "TextToSpeech" does seem better than "TTS".  Some other
>     options include "SpeechSynthesis" and "SpeechSynthesizer".
>     Kind regards,
>     Adam
>     ------------------------------------------------------------------------
>     From: gshires@google.com <mailto:gshires@google.com>
>     Date: Tue, 15 May 2012 10:02:54 -0700
>     To: public-speech-api@w3.org <mailto:public-speech-api@w3.org>
>     Subject: Rename "TTS" object to "TextToSpeech"
>
>
>     I propose we rename the "TTS" object "TextToSpeech".
>
>     There seems to be agreement that TTS is too short [1], and is an
>     acronym that may not be familiar to some developers.
>     TextToSpeech adds clarity, while still being reasonably short and
>     easy to spell.
>
>     [1]
>     http://lists.w3.org/Archives/Public/public-speech-api-contrib/2012Apr/0005.html
>
>     /Glen Shires
>
>
Received on Tuesday, 15 May 2012 19:50:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 May 2012 19:50:26 GMT