- From: Bjorn Bringert <bringert@google.com>
- Date: Thu, 4 Nov 2010 20:58:05 +0100
- To: David Bolter <david.bolter@gmail.com>
- Cc: public-xg-htmlspeech@w3.org
- Message-ID: <AANLkTin=v4D1TrEdEoxJE4TwNrL6Z1zUh2vpB0jy5j0g@mail.gmail.com>
1. I don't think that any further programmatic API is needed. The DOM interface allows creating new HTMLTtsElement instances and gives you programmatic access to all the features. This is the same as for the HTML5 audio API. There should probably be an example of such usage in the proposal. 2. There can be any number of <tts> elements in the document (just like <audio>). You can also reuse the same element and change the content from JavaScript. /Bjorn On Thu, Nov 4, 2010 at 5:10 PM, David Bolter <david.bolter@gmail.com> wrote: > Hi Bjorn, > > I like that web developers can potentially reuse existing knowledge of > audio elements with your spec. > > My initial questions: > > 1. Are you thinking this approach can exist alongside a more programmatic > API? Or do you think this should be *the* TTS support for HTML? > 2. I'm assuming there can be more than one <tts> element per document, > correct? > > Cheers, > David > > > On 04/11/10 11:08 AM, Bjorn Bringert wrote: > >> I have attached a proposal for how we could add TTS support to HTML by >> introducing a<tts> element that shares a lot of functionality with >> <audio>. >> >> This is based on an earlier version that I linked to in a thread in >> September ( >> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2010Sep/0018.html >> ). >> The main differences are in examples, clarifications, formatting, and >> handling of SSML<mark> elements. >> >> > -- Bjorn Bringert Google UK Limited, Registered Office: Belgrave House, 76 Buckingham Palace Road, London, SW1W 9TQ Registered in England Number: 3977902
Received on Thursday, 4 November 2010 19:58:36 UTC