Re: Proposal to add start, stop, and update events to TTS

I've updated the spec to split the onupdate event into onmark and
onboundary events.
https://dvcs.w3.org/hg/speech-api/rev/bcdb6368a448

As always, the current draft spec is at:
http://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html

/Glen Shires



On Mon, Oct 8, 2012 at 9:48 AM, Glen Shires <gshires@google.com> wrote:

>
> I've updated the spec with the those changes: specifically: added
> SpeechSynthesisEvent to replace multiple callback params, and updated TTS
> Example 2 to use it. (Note that Examples section is non-normative.)
> https://dvcs.w3.org/hg/speech-api/rev/813eb945bb04
> As always, the current draft spec is at:
> http://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html
>
> /Glen Shires
>
>
> On Mon, Oct 8, 2012 at 8:52 AM, Dominic Mazzoni <dmazzoni@google.com>wrote:
>
>> On Fri, Oct 5, 2012 at 9:34 AM, Glen Shires <gshires@google.com> wrote:
>>
>>> name attribute
>>>   For onmark events, returns the name of the marker, as defined in SSML
>>> as the name attribute of a mark element. [SSML] For onboundary
>>> events, returns the type of boundary that caused the event: "word" or
>>> "sentence".  For all other events, this value should return undefined.
>>>
>>
>> This is great. It allows for later expanding to "phrase" or "syllable" or
>> "phoneme" without needing to expand the spec a lot, which is what I was
>> hoping for.
>>
>> - Dominic
>>
>>
>

Received on Monday, 8 October 2012 21:43:00 UTC