W3C home > Mailing lists > Public > public-tt@w3.org > May 2013

Re: TTML Agenda for 15/05/13 - Proposed updates to charter

From: Pierre-Anthony Lemieux <pal@sandflow.com>
Date: Thu, 16 May 2013 19:35:51 -0700
Message-ID: <CAF_7JxBn-xs61BwAQeCk+tA3bMLaNDKp8-tXyCNFFCKjp+CSBA@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: Michael Jordan <mijordan@adobe.com>, "public-tt@w3.org" <public-tt@w3.org>
Hi Silvia,

> Yes... but that is unrelated to having TTML support in the browser.

Well, if JS can create cues interactively, can't JS take a TTML
document and, using the API, turn it into something that the browser
will render?


-- Pierre

On Thu, May 16, 2013 at 7:12 PM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com> wrote:
> On Fri, May 17, 2013 at 12:03 PM, Pierre-Anthony Lemieux
> <pal@sandflow.com> wrote:
>>> Because most browsers have refused to implement TTML support in the past.
>> But browsers intend to implement the TextTrackAPI, and the
>> TextTrackAPI is read-write, i.e. one can both read and create cues,
>> right?
> Yes... but that is unrelated to having TTML support in the browser.
> What TTML in the browser means is that there is a specification for
> TTMLCue() (such that cues get exposed to the browser and a JS
> interface is available), and that a browser has decided to parse TTML
> files int a TextTrack and create TTMLCues from that file. The first
> half is part of the charter. The second half requires browsers to
> decide to implement TTML support. IE10 is the only browser this far
> that has decided to implement TTML file parsing, but it has not
> implemented a JS API for TTML content.
> HTH.
> Regards,
> Silvia.
Received on Friday, 17 May 2013 02:36:43 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:09 UTC