- From: Cyril Concolato <cyril.concolato@telecom-paristech.fr>
- Date: Thu, 22 Oct 2015 16:31:42 +0200
- To: public-texttracks@w3.org
Le 22/10/2015 16:21, Philip Jägenstedt a écrit : > On Thu, Oct 22, 2015 at 4:12 PM, Cyril Concolato > <cyril.concolato@telecom-paristech.fr> wrote: >> Le 22/10/2015 16:02, Philip Jägenstedt a écrit : >>> On Thu, Oct 22, 2015 at 3:40 PM, Cyril Concolato >>> <cyril.concolato@telecom-paristech.fr> wrote: >>>> I agree that "if you don't know all of the style up front" you have a >>>> problem to solve. Nigel already pointed that out, as being useful in >>>> broadcast where you don't necessarily know in advance all your styles. To >>>> me, there are 2 main approaches: using timed styles or refreshing untimed >>>> styles. >>> I suspect that timed styles would be tricky to implement, in >>> particular if one considers the ability to "animate" a single cue by >>> having many timed style blocks between the cue's start and end points. >> Can you give an example ? > 00:00.000 --> 00:10.000 > this is a cue > > STYLE 00:00.000 --> 00:01.000 (or whatever the syntax would be) > color: red; > > STYLE 00:01.000 --> 00:02.000 > color: green; > > And so on. Thanks. I would restrict the cues such that styles applying to a cue appear before the cue but indeed you can make funny things that you could not do with style headers. > It would mean that now it's not just the start and end of > cues that would have to tracked, but one would also need a separate > list of timed stylesheets and some way of removing stylesheets at > their end times. Indeed, with timed styles, you would have to track the styles activation/deactivation. That's a drawback. The advantage is more flexibility for delivery. -- Cyril Concolato Multimedia Group / Telecom ParisTech http://concolato.wp.mines-telecom.fr/ @cconcolato
Received on Thursday, 22 October 2015 14:32:11 UTC