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

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

From: Glenn Adams <glenn@skynav.com>
Date: Thu, 16 May 2013 21:01:04 -0600
Message-ID: <CACQ=j+fBq4vDCRi43V9uZUF3jr51vWhZ7U7e+VvjonqeE-Gh8A@mail.gmail.com>
To: Pierre-Anthony Lemieux <pal@sandflow.com>
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Michael Jordan <mijordan@adobe.com>, "public-tt@w3.org" <public-tt@w3.org>
On Thu, May 16, 2013 at 8:55 PM, Pierre-Anthony Lemieux <pal@sandflow.com>wrote:

> > 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
>

In the second option above, it isn't clear to me what role the JS takes.
I'm assuming that the JS is not parsing TTML or constructing cues, but
merely making use of cues (as it desires) in a manner that would occur if
it was a VTT document and the UA is constructing cues.


>
> 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 03:01:56 UTC

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