Re: [HTML Speech] Text to speech

Perhaps someone can explain why TTS is so different to other media (such as
pre-recorded audio) that it warrants a fork from HTML 5's standard mechanism
and justifies a separate JS API? I think the case for HTMLMediaElement is
very compelling for the reasons Bjorn stated.

Dave

On Fri, Sep 10, 2010 at 2:32 AM, david bolter <david.bolter@gmail.com>wrote:

> Hi.
> I tend to agree with Olli here. It seems more straightforward to me to
> provide programmatic tts API which would give web devs a lot of control over
> presentation. I confess though that I've never used a declarative based tts
> library.
>
> In any event I think js devs would like a tts api.
>
> Cheers,
> David
>
> On Sep 9, 2010 4:20 PM, "Bjorn Bringert" <bringert@google.com> wrote:
>
> On Thu, Sep 9, 2010 at 9:06 PM, Olli Pettay <Olli.Pettay@helsinki.fi>
> wrote:
> > On 09/09/2010 06:56 P...
>
> Sure, that would work too. But why introduce new APIs when
> HTMLMediaElement has pretty much all that's needed? Adding a JS API
> would require adding all the methods for playing, pausing, looping,
> autobuffering, getting events, changing source etc. HTMLMediaElement
> already has APIs for all that. It really just boils done to the choice
> between HTML and JavaScript I guess, and adding a <tts> element seemed
> most in line with HTML5.
>
> Also, HTMLMediaElement allows showing UI controls by just setting an
> attribute. If it were solely a JavaScript API, web app developers
> would have to build their own control UIs.
>
>
>
> >>> I think<audio>  is suboptimal even for server-side TTS, for the
> following
> >>> reasons/requirem...
>
> --
> Bjorn Bringert
> Google UK Limited, Registered Office: Belgrave House, 76 Buckingham
> Palace Road, ...
>
>