- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Wed, 10 Jul 2013 14:13:27 +1000
- To: David Singer <singer@apple.com>
- Cc: Simon Pieters <simonp@opera.com>, "public-texttracks@w3.org" <public-texttracks@w3.org>, Rick Eyre <rick.eyre@hotmail.com>
On Tue, Jul 9, 2013 at 7:28 PM, David Singer <singer@apple.com> wrote: > > On Jul 8, 2013, at 8:09 , Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > >> On Wed, Jun 26, 2013 at 9:44 AM, Simon Pieters <simonp@opera.com> wrote: >>> On Wed, 26 Jun 2013 01:14:33 +0200, Rick Eyre <rick.eyre@hotmail.com> wrote: >>> >>>>> The spec is unambiguous, as far as I can tell. The voice isn't rendered >>>>> by >>>>> default, and there's no tooltip. >>>>> >>>>> I think the voice is basically supposed to be a semantic version of >>>>> colored lines, which are commonly used for separating voices. However >>>>> it's >>>>> currently up to the author to provide CSS to get the colors. >>>>> >>>>> We could change the spec, of course, if there are good reasons. >>>> >>>> >>>> My first thought is that there should be some kind of default display for >>>> voice text. If it's something that people are going to be wanting to use a >>>> lot, which I would think it is, then it would make sense to have some kind >>>> of default that people don't have to worry about it. >>> >>> >>> I don't really disagree. However, if the default is something that people >>> *don't* want, then that might be worse, since authors might not figure out >>> how to undo it and instead avoid using voices. >> >> Is there a suggestion for a default rendering of voice tags of VTTCues? >> For example, should >> >> <v Richard>I need a coffee >> >> be rendered as >> >> <bold>Richard:</bold> I need a coffee >> >> ? > > I think it *could* be. I guess the CSS way to do that is to have a rule that does text-before on 'Richard' cues. But 'should'? Looking at it from an author's point-of-view: why author voice tags when they have no visual effect? Silvia.
Received on Wednesday, 10 July 2013 04:14:13 UTC