@aboba > Instead, I'd ask that API to solve it without workarounds. As already stated, the Web Speech API is essentially dead. Filed issues at least over a year ago to implement SSML parsing at both Chromium and Firefox. The fix is relatively simple and the patch has already been posted (https://bugs.chromium.org/p/chromium/issues/detail?id=795371#c18). ChromiumOS authors, again, focus on extension code using `espeak-ng` https://chromium.googlesource.com/chromiumos/third_party/espeak-ng/+/refs/heads/chrome, instead of actually working on the Web Speech API. Besides, am banned from WICG for 1,000 years and when joined the W3C (https://lists.w3.org/Archives/Public/public-wicg/2019Oct/0000.html) to contribute to Web Speech API, was un-joined from that parent organization, for fraudualent reasoning easily proven hypocritical  . Have zero confidence that W3C and especially WICG are operating in a non-biased manner. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/629#issuecomment-572645296 using your GitHub accountReceived on Thursday, 9 January 2020 16:40:36 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:49 UTC
