- From: David Singer <singer@apple.com>
- Date: Mon, 09 Dec 2013 10:49:12 -0800
- To: Silvia Pfieffer <silviapfeiffer1@gmail.com>
- Cc: Victor Cărbune <vcarbune@chromium.org>, Glenn Adams <glenn@chromium.org>, Silvia Pfeiffer <silviapf@chromium.org>, "public-texttracks@w3.org" <public-texttracks@w3.org>, Nigel Megitt <nigel.megitt@bbc.co.uk>
On Dec 8, 2013, at 19:16 , Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: >>> I fully expect that more than half of these >>> features are not encodable or translatable to WebVTT, or if they are, then >>> have the added disadvantage of having to maintain a separate CSS style sheet >>> containing rules that apply to specific VTT files. > > Why is that a disadvantage? Separating the styling from the content > has been a driving design principle of the Web and has been part of > the cause for the success of HTML. I don't see how that would be a > disadvantage. I think that many think of this as an *advantage*; that VTT re-uses and leverages the web platform, including CSS. David Singer Multimedia and Software Standards, Apple Inc.
Received on Monday, 9 December 2013 18:49:40 UTC