Rather unceremoniously, Google began rolling out a new, more natural voice for its Now assistant last week. The first official acknowledgement of the voice comes in Nat & Lo’s newest video, which shows how the voice was made and offers a nice primer on the history and work behind text-to-speech.
Following the release of Chrome 32 on Google’s stable release channel, today Chrome 33 has moved into beta bringing access to Custom Elements, a Web Speech API for speech recognition and synthesis, and more. The new Custom Elements will allow developers to add new HTML elements in web applications in “much cleaner ways” as highlighted by Google in the sample code for a chat app above. With the spec developers will able to:
The release also includes access to the Web Speech API for adding speech recognition and synthesis features to web pages. Google gives the example of dictations being “synthesized to play back in a different language.” Google described some of the other updates in the release including the availability of the requestAutocomplete API for easily implementing web payments on Mac:
Other web platform changes in this release
As noted by the unofficial Google Operating System blog, Google could soon add the option to select a dialect for certain languages in its text-to-speech feature within Google Translate. The option is currently hidden in Translate’s source code, according to the report, and it would allow users to hear various dialects like American, British, and Australian for English.
The text-to-speech feature will allow you to select the dialect for languages like English, Spanish, Portuguese and Chinese. It’s nice to compare American English, British English and Australian English.
The report also noted hints of other features that aren’t currently available, including phrasebook and dictionary features.
