- From: Philip Jägenstedt <foolip@google.com>
- Date: Wed, 29 Aug 2018 13:50:17 +0200
- To: Dominic Mazzoni <dmazzoni@google.com>
- Cc: public-speech-api@w3.org
Received on Wednesday, 29 August 2018 11:50:51 UTC
I found implementation bugs for all engines and pasted them in https://github.com/w3c/speech-api/issues/37. It sounds like this is a feature that would be appreciated, despite the lack of implementer interest so far. Let's use the issue to discuss. On Mon, Aug 27, 2018 at 5:22 PM Dominic Mazzoni <dmazzoni@google.com> wrote: > We've received a number of requests to implement SSML support in Chrome. > I'd be hesitant to completely abandon the idea, though we should be > completely upfront about the fact that it's not implemented yet. > > If we do implement it, perhaps there should be a way for voices to > explicitly identify that they support SSML, that way clients would be able > to safely include SSML only if the engine will be interpreting it. > > - Dominic > > On Mon, Aug 20, 2018 at 6:11 AM Philip Jägenstedt <foolip@google.com> > wrote: > >> I've just tested SSML support and filed >> https://github.com/w3c/speech-api/issues/37 where I suggest that if >> there is no implementer interest, those bits should be removed from the >> spec. >> >> Pointing to it here also so that it gets wider attention. Does anybody >> plan to implement the SSML bits of the spec? >> >> Thanks! >> >
Received on Wednesday, 29 August 2018 11:50:51 UTC