Re: Timed tracks

On Fri, May 7, 2010 at 11:02 AM, Sean Hayes <Sean.Hayes@microsoft.com> wrote:
> I would point out however that a lot of the resistance TTML has had in the past is due to the perception that it is already too complex, so adding all this CSS3 stuff, while fun and in some cases justifiable; will only serve to make it more so.  I'm also somewhat confused as to why on the one hand you want SRT, which is utterly minimalist and on the other you want this extreme complexity.

Note the *extremely* important difference between *allowing* this sort
of complexity via CSS for UAs that support CSS, and *requiring* it as
a fundamental part of the format that text tracks are specified in.

WebSRT does not require CSS, though it does define how CSS can
interact with it.  A UA that doesn't support any CSS can still display
a WebSRT file in a completely acceptable manner.  A WebSRT-supporting
UA just has to be able to handle italic, bold, ruby, newlines, and
bidi text, plus a little bit of positioning.

Note as well that we don't want SRT.  It is indeed too minimalist to
handle enough of the use-cases that were found.  But it provides a
base from which to develop WebSRT, and doesn't require complexity that
we don't need.

~TJ

Received on Friday, 7 May 2010 18:16:10 UTC