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

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

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 17 May 2013 12:41:00 +1000
Message-ID: <CAHp8n2=5FXh__gFt_iKRWdrOBOt+b0TPZtm6T-jHtM+eFDHmfQ@mail.gmail.com>
To: Glenn Adams <glenn@skynav.com>
Cc: Pierre-Anthony Lemieux <pal@sandflow.com>, Michael Jordan <mijordan@adobe.com>, "public-tt@w3.org" <public-tt@w3.org>
On Fri, May 17, 2013 at 12:14 PM, Glenn Adams <glenn@skynav.com> wrote:
> On Thu, May 16, 2013 at 7:35 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
> wrote:
>> On Fri, May 17, 2013 at 11:18 AM, Pierre-Anthony Lemieux
>> <pal@sandflow.com> wrote:
>> > Hi Silvia et al.,
>> >
>> >> Think about a sw developer who has a TTML file and wants to translate
>> >> it to a WebVTT file to be rendered in a Web browser that only supports
>> >> WebVTT.
>> >
>> > If there is a mapping between TTML and the TextTrackAPI, i.e. a
>> > mapping between TTML and HTML 5, why would one need to translate the
>> > file?
>> Because most browsers have refused to implement TTML support in the past.
> I don't believe this is relevant because it is certain to change. There is
> no reason UAs shouldn't be implementing TTML support directly. We have to
> assume and plan on this in fact.

I'm not being rhetoric here - I am simply stating a fact. I chose my
words carefully and added "...in the past", because it may indeed

That fact is not relevant to this discussion, though, because there
will always be a need to convert between formats. TTML <-> WebVTT is
just one format conversion that is needed. I simply chose an example
of something that people need to do today for some browsers if they
want to make use of native caption format rendering capabilities of

Received on Friday, 17 May 2013 02:41:47 UTC

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