Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
A W3C recommendation that is now embraced by Google cloud TTS (text to speech) and Amazon cloud TTS
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
This doesn't seem to be a web browser API? CanIUse doesn't track purely server-side standards.
@cvrebert The API is not server-based. SSML parsing simply has not been implemented by browsers, for various reasons.
Relevant browser inquiries, issues, bugs https://lists.w3.org/Archives/Public/www-voice/2017OctDec/0000.html; https://bugs.chromium.org/p/chromium/issues/detail?id=88072; https://bugs.chromium.org/p/chromium/issues/detail?id=795371; https://bugs.chromium.org/p/chromium/issues/detail?id=806592; https://bugzilla.mozilla.org/show_bug.cgi?id=1425523; which collectively appear to indicate a lack of will to implement SSML parsing at the browser by the maintainers ("owners") of Web Speech API at the browsers, particularly where, at least for Chromium/Chrome, the patch kindly provided by speech-dispatcher maintainers https://github.com/brailcom/speechd (see brailcom/speechd#1 (comment); https://bugs.chromium.org/p/chromium/issues/attachmentText?aid=322294) would immediately enable SSML parsing when espeak or espeak-ng is the underlying speech module used by the browser; at Firefox the only reply was "UNTRIAGED".
No branches or pull requests