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:55:19 -0700
Message-ID: <CAF_7JxAdGsKw32_z3wtUarN9u8o0aj9=_51usjutCWwjgbzRKg@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: Michael Jordan <mijordan@adobe.com>, "public-tt@w3.org" <public-tt@w3.org>
> Yes, you can. You can do that with any format. However, that means
> that JS supports the TTML format, not the browser.

So shouldn't the following two processes roughly equivalent? If not, why?

TTML document ---------> WebVTT document -----------> UA
TTML document ----JS----> sequence of calls to TextTrack API

Thanks,

-- Pierre

On Thu, May 16, 2013 at 7:38 PM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com> wrote:
> On Fri, May 17, 2013 at 12:35 PM, Pierre-Anthony Lemieux
> <pal@sandflow.com> wrote:
>> 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?
>
> Yes, you can. You can do that with any format. However, that means
> that JS supports the TTML format, not the browser.
>
> Regards,
> Silvia.
Received on Friday, 17 May 2013 02:56:07 UTC

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