- From: David Singer <singer@apple.com>
- Date: Mon, 23 Feb 2015 11:46:10 -0800
- To: Silvia Pfieffer <silviapfeiffer1@gmail.com>
- Cc: Jeroen Wijering <jeroen@jwplayer.com>, Steve Heffernan <steve@zencoder.com>, John Luther <jluther@jwplayer.com>, Philip Jägenstedt <philipj@opera.com>, "public-texttracks@w3.org" <public-texttracks@w3.org>, Richard Eyre <rick.eyre@hotmail.com>, gkatsevman@brightcove.com
> On Feb 21, 2015, at 23:10 , Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > > Note that I have made a new suggestion as to how to deal with inline > styles in VTT. > https://www.w3.org/Bugs/Public/show_bug.cgi?id=15023#c15 > > If that is agreeable and it is a requirement to be added before we go > to CR, I can write the spec for that (assuming Philip agrees with the > proposed approach). we had a long discussion on this several years back. I’ll try to resurrect the questions 1) can new styles occur only in the header, or throughout the file? I commented on the bug: currently VTT files are beautifully incremental and random accessible; allowing styles to occur anywhere and persist to end of file would badly impact that. Can we do the 90%+ case and have styles only at the beginning, please? I don’t mind if they are ‘part of’ the header or just after it and before the first cue. 2) What about multi-line? We either need a syntax that allows blank lines, or an escape for them. Years back, we suggested escape. But removing blank lines is as easy as escaping them, and has the huge advantage that the result is still valid CSS. What other basic design choices are there, that we could debate? > > Cheers, > Silvia. > > > > On Tue, Jan 20, 2015 at 7:39 AM, Jeroen Wijering <jeroen@jwplayer.com> wrote: >> With JW Player, we implemented basic parsing of cues and rendering of >> cues according to the draft spec. Especially in the area of rendering, >> the spec is well defined and very helpful to implementors. With TTML >> and SRT, we had to be much more creative in doing the rendering. Let >> me know what exactly you'd like to see in terms of feedback on the >> spec; our player engineers can put that together. >> >> We have not yet implemented regions. It's a bit hard to comment on the >> spec without doing the work; you always find the small details when >> implementing. It reads very defined and focused to the use case though >> (608 compatibility). If you require comments from people that have >> implemented the spec, we could look into prioritizing this work for JW >> Player. >> >> The one item I'm missing from the spec is inline CSS, but that's >> pushed to V2 right? >> (https://www.w3.org/Bugs/Public/show_bug.cgi?id=15023) On platforms >> like Flash or native Android, we'd like to have all cue styling inline >> since there's no CSS. Publisher also need it when converting from >> legacy formats (608, TTML) into VTT. In these formats, the styling >> also "lives" inline. >> >> - Jeroen >> >> >> >> On Wed, Jan 14, 2015 at 4:40 PM, Steve Heffernan <steve@zencoder.com> wrote: >>> I've CC'd Gary Katsevman who's done the most work with the vtt spec for >>> Video.js. Gary, how do you feel about the state of the VTT spec? Did you run >>> into any issues that could be submitted as a bug? >>> >>> Also CC'd Rick Eyre (mozilla/vtt.js) though he's probably already on the >>> list. >>> >>> -Steve >> >> David Singer Manager, Software Standards, Apple Inc.
Received on Monday, 23 February 2015 19:46:43 UTC