- From: <bugzilla@jessica.w3.org>
- Date: Fri, 08 Jul 2011 12:28:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13184 --- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2011-07-08 12:28:45 UTC --- http://lists.w3.org/Archives/Public/public-html/2011Jul/0150.html While nested chapters are not overly common, we can easily support the use case simply by considering cues which are contained (time range-wise, not syntactically) within another to create a child chapter, as such: WEBVTT 00:00:00.000 --> 00:00:10.700 Title Slide 00:00:10.700 --> 00:00:47.600 Introduction by Naomi Black 00:00:47.600 --> 00:07:37.900 Talk on WebVTT 00:00:47.600 --> 00:01:50.100 Impact of Captions on the Web 00:01:50.100 --> 00:03:33.000 Requirements of a Video text format 00:03:33.000 --> 00:04:57.766 Simple WebVTT file 00:04:57.766 --> 00:06:16.666 Styled WebVTT file 00:06:16.666 --> 00:07:37.900 Internationalized WebVTT file The hierarchy here is: 1. Title Slide 2. Introduction by Naomi Black 3. Talk on WebVTT 3.1. Impact of Captions on the Web 3.2. Requirements of a Video text format 3.3. Simple WebVTT file 3.4. Styled WebVTT file 3.5. Internationalized WebVTT file What's needed in the spec is to specify a simple algorithm for constructing the tree and say that they may expose in UI and to AT this tree. One algorithm was suggested in <http://lists.w3.org/Archives/Public/public-html/2011Jul/0119.html>, but anything will do. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 8 July 2011 12:28:47 UTC