W3C home > Mailing lists > Public > public-html-commits@w3.org > May 2010

html5/spec Overview.html,1.4081,1.4082

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 05 May 2010 21:17:21 +0000
To: public-html-commits@w3.org
Message-Id: <E1O9ly5-0002HY-BM@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv8756

Modified Files:
	Overview.html 
Log Message:
Captions - Stage 9.1: More parser rules for WebSRT. (whatwg r5080)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4081
retrieving revision 1.4082
diff -u -d -r1.4081 -r1.4082
--- Overview.html	5 May 2010 20:22:45 -0000	1.4081
+++ Overview.html	5 May 2010 21:17:17 -0000	1.4082
@@ -22767,6 +22767,12 @@
 
   <p class="XXX">...
 
+  <!-- XXX
+   Make sure that .cues and .activeCues doesn't change while script is
+   running, except for addCue/removeCue and the removal of all cues in
+   the face of a dynamic track.src change.
+  -->
+
   </div><h6 id="cue-events"><span class="secno">4.8.10.10.5 </span>Event definitions</h6><p class="XXX">...
 
 <!-- XXX
@@ -22817,15 +22823,21 @@
 
   <h6 id="parsing-0"><span class="secno">4.8.10.11.2 </span>Parsing</h6>
 
-  <p>A <dfn id="websrt-parser">WebSRT parser</dfn>, given an input byte stream, must
-  convert the bytes into Unicode characters by interpreting them as
-  UTF-8. Bytes or sequences of bytes that are not valid UTF-8
-  sequences must be interpreted as a U+FFFD REPLACEMENT CHARACTER. All
-  U+0000 NULL characters must be replaced by U+FFFD REPLACEMENT
-  CHARACTERs.</p>
+  <p>A <dfn id="websrt-parser">WebSRT parser</dfn>, given an input byte stream and a
+  <a href="#timed-track-list-of-cues">timed track list of cues</a> <var title="">output</var>,
+  must convert the bytes into a string of Unicode characters by
+  interpreting them as UTF-8, and then must parse the resulting string
+  according to the <a href="#websrt-parser-algorithm">WebSRT parser algorithm</a> below. A
+  <a href="#websrt-parser">WebSRT parser</a>, specifically its conversion and parsing
+  steps, is typically run asynchronously, with the input byte stream
+  being updated incrementally as the resource is downloaded.</p>
 
-  <p>The Unicode characters from a string that must be parsed
-  according to the following algorithm:</p>
+  <p>When convering the bytes into Unicode characters, bytes or
+  sequences of bytes that are not valid UTF-8 sequences must be
+  interpreted as a U+FFFD REPLACEMENT CHARACTER, and all U+0000 NULL
+  characters must be replaced by U+FFFD REPLACEMENT CHARACTERs.</p>
+
+  <p>The <dfn id="websrt-parser-algorithm">WebSRT parser algorithm</dfn> is as follows:</p>
 
   <ol><li><p>Let <var title="">input</var> be the string being
    parsed.</li>
@@ -22833,6 +22845,19 @@
    <li><p>Let <var title="">position</var> be a pointer into <var title="">input</var>, initially pointing at the start of the
    string.</li>
 
+   <li><p><a href="#collect-a-sequence-of-characters">Collect a sequence of characters</a> that are
+   either U+000D CARRIAGE RETURN (CR) or U+000A LINE FEED (LF)
+   characters.</li>
+
+   <li><p><a href="#collect-a-sequence-of-characters">Collect a sequence of characters</a> that are
+   <em>not</em> U+000D CARRIAGE RETURN (CR) or U+000A LINE FEED (LF)
+   characters. Let <var title="">line</var> be those
+   characters, if any.</li>
+
+   <li><p>If <var title="">line</var> is the empty string, then the
+   file has ended. Abort these steps. The <a href="#websrt-parser">WebSRT parser</a>
+   has finished.</li>
+
    <li><p class="XXX">...</li>
 
   </ol></div><h5 id="user-interface"><span class="secno">4.8.10.12 </span>User interface</h5><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>The <dfn id="attr-media-controls" title="attr-media-controls"><code>controls</code></dfn>
Received on Wednesday, 5 May 2010 21:17:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 5 May 2010 21:17:23 GMT