- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 8 Sep 2010 07:54:38 -0700
On Wed, Sep 8, 2010 at 2:27 AM, Philip J?genstedt <philipj at opera.com> wrote: > On Wed, 08 Sep 2010 01:19:17 +0200, Ian Hickson <ian at hixie.ch> wrote: >> We could say that a custom voice has to start with some punctuation or >> other, say <:philip>? > > Yes, that would be better than numerical voices IMO. Unless there's a very > good reason for making voices always apply to the whole cue, could we not > use the same parsing for voices and other tags (i, b, ruby, rt)? > > Ideally, the CSS extensions > (http://wiki.whatwg.org/wiki/Timed_tracks#CSS_extensions) should also work > the same for voices and tags, using the normal child selectors would work. > Something like video::cue(narrator > i) to style the following cue: > > 00:01.000 --> 00:02.000 > <narrator><i>The story begins > > I'm not sure what constraints CSS syntax puts on the prefix for custom > voices, is : safe? Other options might be <@philip> (Twitter style) or > <-philip> (vendor prefix style). A token preceded by a : is just treated as a pseudoclass by the grammar. That's not necessarily a bad thing, though. I believe - should be just fine. @ would be too. ~TJ
Received on Wednesday, 8 September 2010 07:54:38 UTC