[html5] r5081 - [giow] (0) Captions - Stage 9.2: More parser rules for WebSRT.
whatwg at whatwg.org
whatwg at whatwg.org
Wed May 5 18:01:56 PDT 2010
Author: ianh
Date: 2010-05-05 18:01:55 -0700 (Wed, 05 May 2010)
New Revision: 5081
Modified:
complete.html
index
source
Log:
[giow] (0) Captions - Stage 9.2: More parser rules for WebSRT.
Modified: complete.html
===================================================================
--- complete.html 2010-05-05 21:17:52 UTC (rev 5080)
+++ complete.html 2010-05-06 01:01:55 UTC (rev 5081)
@@ -186,7 +186,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<hgroup><h1>Web Applications 1.0</h1>
- <h2 class="no-num no-toc">Draft Standard — 5 May 2010</h2>
+ <h2 class="no-num no-toc">Draft Standard — 6 May 2010</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -1311,7 +1311,7 @@
<li><a href=#application/xhtml+xml><span class=secno>16.3 </span><code>application/xhtml+xml</code></a></li>
<li><a href=#text/cache-manifest><span class=secno>16.4 </span><code>text/cache-manifest</code></a></li>
<li><a href=#text/ping><span class=secno>16.5 </span><code>text/ping</code></a></li>
- <li><a href=#text/websrt><span class=secno>16.6 </span><code>text/websrt</code></a></li>
+ <li><a href=#text/srt><span class=secno>16.6 </span><code>text/srt</code></a></li>
<li><a href=#application/microdata+json><span class=secno>16.7 </span><code>application/microdata+json</code></a></li>
<li><a href=#ping-from><span class=secno>16.8 </span><code>Ping-From</code></a></li>
<li><a href=#ping-to><span class=secno>16.9 </span><code>Ping-To</code></a></ol></li>
@@ -26267,7 +26267,8 @@
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>
+ being updated incrementally as the resource is downloaded; this is
+ called an <dfn id=incremental-websrt-parser>incremental WebSRT parser</dfn>.</p>
<p>When convering the bytes into Unicode characters, bytes or
sequences of bytes that are not valid UTF-8 sequences must be
@@ -26280,23 +26281,58 @@
parsed.</li>
<li><p>Let <var title="">position</var> be a pointer into <var title="">input</var>, initially pointing at the start of the
- string.</li>
+ string. In an <a href=#incremental-websrt-parser>incremental WebSRT parser</a>, when this
+ algorithm (or further algorithms that it uses) moves the <var title="">position</var> pointer, the user agent must wait until
+ appropriate further characters from the byte stream have been added
+ to <var title="">input</var> before moving the pointer, so that the
+ algorithm never reads past the end of the <var title="">input</var>
+ string. Once the byte stream has ended, and all characters have
+ been added to <var title="">input</var>, then the <var title="">position</var> pointer may, when so instructed by the
+ algorithms, be moved past the end of <var title="">input</var>.</li>
+ <li><p><i>Cue loop</i>: <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>Let <var title="">id</var> be the empty 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>
+ <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 jump
+ to the step labeled <i>end</i>.</li>
+
+ <li><p>If <var title="">line</var> contains the three-character
+ substring "<code title="">--></code>" (U+002D HYPHEN-MINUS, U+002D
+ HYPHEN-MINUS, U+003E GREATER-THAN SIGN), then jump to the step
+ labeled <i>timing</i> below.</li>
+
+ <li><p>Let <var title="">id</var> be <var title="">line</var>.<p></li>
+
+ <li><p>If <var title="">position</var> is past the end of <var title="">input</var>, then jump to the step labeled
+ <i>end</i>.</li>
+
+ <li><p>If the character indicated by <var title="">position</var>
+ is a U+000D CARRIAGE RETURN (CR) character, advance <var title="">position</var> to the next character in <var title="">input</var>.</li>
+
+ <li><p>If the character indicated by <var title="">position</var>
+ is a U+000A LINE FEED (LF) character, advance <var title="">position</var> to the next character in <var title="">input</var>.</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>
+ 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>If <var title="">line</var> is the empty string, then jump
+ to the step labeled <i>cue loop</i>.</li>
- <li><p class=XXX>...</li>
+ <li><p><i>Timings</i>: <span class=XXX>...</span></li>
+ <li><p><i>End</i>: The file has ended. Abort these steps. The
+ <a href=#websrt-parser>WebSRT parser</a> has finished.</li>
+
</ol></div>
@@ -86981,7 +87017,7 @@
<code><a href=#text/ping>text/ping</a></code> resources.</p>
<!--PING-->
- <h3 id=text/websrt><span class=secno>16.6 </span><dfn><code>text/websrt</code></dfn></h3>
+ <h3 id=text/srt><span class=secno>16.6 </span><dfn><code>text/srt</code></dfn></h3>
<p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p>
@@ -86994,7 +87030,7 @@
<dl><dt>Type name:</dt>
<dd>text</dd>
<dt>Subtype name:</dt>
- <dd>websrt</dd>
+ <dd>srt</dd>
<dt>Required parameters:</dt>
<dd>No parameters</dd>
<dt>Optional parameters:</dt>
@@ -87045,7 +87081,7 @@
<dt>Change controller:</dt>
<dd>WHATWG</dd>
</dl><p>Fragment identifiers have no meaning with
- <code><a href=#text/websrt>text/websrt</a></code> resources.</p>
+ <code>text/websrt</code> resources.</p>
Modified: index
===================================================================
--- index 2010-05-05 21:17:52 UTC (rev 5080)
+++ index 2010-05-06 01:01:55 UTC (rev 5081)
@@ -190,7 +190,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<hgroup><h1>HTML5 (including next generation additions still in development)</h1>
- <h2 class="no-num no-toc">Draft Standard — 5 May 2010</h2>
+ <h2 class="no-num no-toc">Draft Standard — 6 May 2010</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -1183,7 +1183,7 @@
<li><a href=#application/xhtml+xml><span class=secno>14.3 </span><code>application/xhtml+xml</code></a></li>
<li><a href=#text/cache-manifest><span class=secno>14.4 </span><code>text/cache-manifest</code></a></li>
<li><a href=#text/ping><span class=secno>14.5 </span><code>text/ping</code></a></li>
- <li><a href=#text/websrt><span class=secno>14.6 </span><code>text/websrt</code></a></li>
+ <li><a href=#text/srt><span class=secno>14.6 </span><code>text/srt</code></a></li>
<li><a href=#application/microdata+json><span class=secno>14.7 </span><code>application/microdata+json</code></a></li>
<li><a href=#ping-from><span class=secno>14.8 </span><code>Ping-From</code></a></li>
<li><a href=#ping-to><span class=secno>14.9 </span><code>Ping-To</code></a></ol></li>
@@ -26168,7 +26168,8 @@
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>
+ being updated incrementally as the resource is downloaded; this is
+ called an <dfn id=incremental-websrt-parser>incremental WebSRT parser</dfn>.</p>
<p>When convering the bytes into Unicode characters, bytes or
sequences of bytes that are not valid UTF-8 sequences must be
@@ -26181,23 +26182,58 @@
parsed.</li>
<li><p>Let <var title="">position</var> be a pointer into <var title="">input</var>, initially pointing at the start of the
- string.</li>
+ string. In an <a href=#incremental-websrt-parser>incremental WebSRT parser</a>, when this
+ algorithm (or further algorithms that it uses) moves the <var title="">position</var> pointer, the user agent must wait until
+ appropriate further characters from the byte stream have been added
+ to <var title="">input</var> before moving the pointer, so that the
+ algorithm never reads past the end of the <var title="">input</var>
+ string. Once the byte stream has ended, and all characters have
+ been added to <var title="">input</var>, then the <var title="">position</var> pointer may, when so instructed by the
+ algorithms, be moved past the end of <var title="">input</var>.</li>
+ <li><p><i>Cue loop</i>: <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>Let <var title="">id</var> be the empty 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>
+ <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 jump
+ to the step labeled <i>end</i>.</li>
+
+ <li><p>If <var title="">line</var> contains the three-character
+ substring "<code title="">--></code>" (U+002D HYPHEN-MINUS, U+002D
+ HYPHEN-MINUS, U+003E GREATER-THAN SIGN), then jump to the step
+ labeled <i>timing</i> below.</li>
+
+ <li><p>Let <var title="">id</var> be <var title="">line</var>.<p></li>
+
+ <li><p>If <var title="">position</var> is past the end of <var title="">input</var>, then jump to the step labeled
+ <i>end</i>.</li>
+
+ <li><p>If the character indicated by <var title="">position</var>
+ is a U+000D CARRIAGE RETURN (CR) character, advance <var title="">position</var> to the next character in <var title="">input</var>.</li>
+
+ <li><p>If the character indicated by <var title="">position</var>
+ is a U+000A LINE FEED (LF) character, advance <var title="">position</var> to the next character in <var title="">input</var>.</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>
+ 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>If <var title="">line</var> is the empty string, then jump
+ to the step labeled <i>cue loop</i>.</li>
- <li><p class=XXX>...</li>
+ <li><p><i>Timings</i>: <span class=XXX>...</span></li>
+ <li><p><i>End</i>: The file has ended. Abort these steps. The
+ <a href=#websrt-parser>WebSRT parser</a> has finished.</li>
+
</ol></div>
@@ -80224,7 +80260,7 @@
<code><a href=#text/ping>text/ping</a></code> resources.</p>
<!--PING-->
- <h3 id=text/websrt><span class=secno>14.6 </span><dfn><code>text/websrt</code></dfn></h3>
+ <h3 id=text/srt><span class=secno>14.6 </span><dfn><code>text/srt</code></dfn></h3>
<p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p>
@@ -80237,7 +80273,7 @@
<dl><dt>Type name:</dt>
<dd>text</dd>
<dt>Subtype name:</dt>
- <dd>websrt</dd>
+ <dd>srt</dd>
<dt>Required parameters:</dt>
<dd>No parameters</dd>
<dt>Optional parameters:</dt>
@@ -80288,7 +80324,7 @@
<dt>Change controller:</dt>
<dd>WHATWG</dd>
</dl><p>Fragment identifiers have no meaning with
- <code><a href=#text/websrt>text/websrt</a></code> resources.</p>
+ <code>text/websrt</code> resources.</p>
Modified: source
===================================================================
--- source 2010-05-05 21:17:52 UTC (rev 5080)
+++ source 2010-05-06 01:01:55 UTC (rev 5081)
@@ -28392,7 +28392,8 @@
according to the <span>WebSRT parser algorithm</span> below. A
<span>WebSRT parser</span>, specifically its conversion and parsing
steps, is typically run asynchronously, with the input byte stream
- being updated incrementally as the resource is downloaded.</p>
+ being updated incrementally as the resource is downloaded; this is
+ called an <dfn>incremental WebSRT parser</dfn>.</p>
<p>When convering the bytes into Unicode characters, bytes or
sequences of bytes that are not valid UTF-8 sequences must be
@@ -28408,23 +28409,67 @@
<li><p>Let <var title="">position</var> be a pointer into <var
title="">input</var>, initially pointing at the start of the
- string.</p></li>
+ string. In an <span>incremental WebSRT parser</span>, when this
+ algorithm (or further algorithms that it uses) moves the <var
+ title="">position</var> pointer, the user agent must wait until
+ appropriate further characters from the byte stream have been added
+ to <var title="">input</var> before moving the pointer, so that the
+ algorithm never reads past the end of the <var title="">input</var>
+ string. Once the byte stream has ended, and all characters have
+ been added to <var title="">input</var>, then the <var
+ title="">position</var> pointer may, when so instructed by the
+ algorithms, be moved past the end of <var
+ title="">input</var>.</p></li>
+ <li><p><i>Cue loop</i>: <span>Collect a sequence of
+ characters</span> that are either U+000D CARRIAGE RETURN (CR) or
+ U+000A LINE FEED (LF) characters.</p></li>
+
+ <li><p>Let <var title="">id</var> be the empty string.</p></li>
+
<li><p><span>Collect a sequence of characters</span> that are
- either U+000D CARRIAGE RETURN (CR) or U+000A LINE FEED (LF)
- characters.</p></li>
+ <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.</p></li>
+ <li><p>If <var title="">line</var> is the empty string, then jump
+ to the step labeled <i>end</i>.</p></li>
+
+ <li><p>If <var title="">line</var> contains the three-character
+ substring "<code title="">--></code>" (U+002D HYPHEN-MINUS, U+002D
+ HYPHEN-MINUS, U+003E GREATER-THAN SIGN), then jump to the step
+ labeled <i>timing</i> below.</p></li>
+
+ <li><p>Let <var title="">id</var> be <var
+ title="">line</var>.<p></li>
+
+ <li><p>If <var title="">position</var> is past the end of <var
+ title="">input</var>, then jump to the step labeled
+ <i>end</i>.</p></li>
+
+ <li><p>If the character indicated by <var title="">position</var>
+ is a U+000D CARRIAGE RETURN (CR) character, advance <var
+ title="">position</var> to the next character in <var
+ title="">input</var>.</p></li>
+
+ <li><p>If the character indicated by <var title="">position</var>
+ is a U+000A LINE FEED (LF) character, advance <var
+ title="">position</var> to the next character in <var
+ title="">input</var>.</p></li>
+
<li><p><span>Collect a sequence of characters</span> 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.</p></li>
+ characters. Let <var title="">line</var> be those characters, if
+ any.</p></li>
- <li><p>If <var title="">line</var> is the empty string, then the
- file has ended. Abort these steps. The <span>WebSRT parser</span>
- has finished.</p></li>
+ <li><p>If <var title="">line</var> is the empty string, then jump
+ to the step labeled <i>cue loop</i>.</p></li>
- <li><p class="XXX">...</p></li>
+ <li><p><i>Timings</i>: <span class="XXX">...</span></p></li>
+ <li><p><i>End</i>: The file has ended. Abort these steps. The
+ <span>WebSRT parser</span> has finished.</p></li>
+
</ol>
</div>
@@ -99143,7 +99188,7 @@
<code>text/ping</code> resources.</p>
<!--START w3c-html--><!--PING-->
- <h3><dfn><code>text/websrt</code></dfn></h3>
+ <h3><dfn><code>text/srt</code></dfn></h3>
<p>This registration is for community review and will be submitted
to the IESG for review, approval, and registration with IANA.</p>
@@ -99157,7 +99202,7 @@
<dt>Type name:</dt>
<dd>text</dd>
<dt>Subtype name:</dt>
- <dd>websrt</dd>
+ <dd>srt</dd>
<dt>Required parameters:</dt>
<dd>No parameters</dd>
<dt>Optional parameters:</dt>
More information about the Commit-Watchers
mailing list