Skip to content
Permalink
Browse files
[e] (0) editorial cleanup and reference collection
git-svn-id: http://svn.whatwg.org/webapps@3246 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jun 14, 2009
1 parent 12bbf14 commit dfa984fd651fafd444e981b8db008c5f5469acea
Showing with 10 additions and 18 deletions.
  1. +5 −9 index
  2. +5 −9 source
14 index
@@ -4779,8 +4779,7 @@
for instance, with a progressively interlaced JPEG or an HTML file,
additional tasks may be queued to process the data as it is
downloaded. The <a href=#task-source>task source</a> for these tasks is the
<a href=#networking-task-source>networking task source</a>.</p> <!-- XXX make sure each
use of 'fetch' defines what the appropriate task is -->
<a href=#networking-task-source>networking task source</a>.</p>

</ol><p class=note>The <a href=#application-cache>application cache</a> processing model
introduces some <a href=#changesToNetworkingModel>changes to the
@@ -4820,10 +4819,6 @@
headers are equivalent to the authentication aspects of the FTP
protocol.</p>

<p class=XXX>If there are any specific questions with what should
be considered equivalent to what, let me know, and I'll make it more
explicit for those cases.</p>


<h4 id=encrypted-http-and-related-security-concerns><span class=secno>2.6.2 </span>Encrypted HTTP and related security concerns</h4>

@@ -4910,8 +4905,7 @@
<p>When comparing a string specifying a character encoding with the
name or alias of a character encoding to determine if they are
equal, user agents must use the Charset Alias Matching rules defined
in Unicode Technical Standard #22. <a href=#refsUTS22>[UTS22]</a></p> <!-- XXXrefs
http://unicode.org/reports/tr22/#Charset_Alias_Matching -->
in Unicode Technical Standard #22. <a href=#refsUTS22>[UTS22]</a></p>

<p class=example>For instance, "GB_2312-80" and "g.b.2312(80)" are
considered equivalent names.</p>
@@ -69942,7 +69936,7 @@ S SPACER STRIKE TT U -->

<!-- XXX check that #refsRFC([0-9]+) is always for [RFC\1] -->

<!--
<!-- REFS

[COMPUTABLE] On computable numbers, with an application to the
Entscheidungsproblem. Alan M. Turing. In Proceedings of the London
@@ -69956,6 +69950,8 @@ S SPACER STRIKE TT U -->

[UNICODECASE] Unicode Standard Annex #21, Case Mappings

[UTS22] http://unicode.org/reports/tr22/#Charset_Alias_Matching

-->


14 source
@@ -4405,8 +4405,7 @@
for instance, with a progressively interlaced JPEG or an HTML file,
additional tasks may be queued to process the data as it is
downloaded. The <span>task source</span> for these tasks is the
<span>networking task source</span>.</p> <!-- XXX make sure each
use of 'fetch' defines what the appropriate task is -->
<span>networking task source</span>.</p>

</ol>

@@ -4449,10 +4448,6 @@
headers are equivalent to the authentication aspects of the FTP
protocol.</p>

<p class="XXX">If there are any specific questions with what should
be considered equivalent to what, let me know, and I'll make it more
explicit for those cases.</p>


<h4>Encrypted HTTP and related security concerns</h4>

@@ -4544,8 +4539,7 @@
name or alias of a character encoding to determine if they are
equal, user agents must use the Charset Alias Matching rules defined
in Unicode Technical Standard #22. <a
href="#refsUTS22">[UTS22]</a></p> <!-- XXXrefs
http://unicode.org/reports/tr22/#Charset_Alias_Matching -->
href="#refsUTS22">[UTS22]</a></p>

<p class="example">For instance, "GB_2312-80" and "g.b.2312(80)" are
considered equivalent names.</p>
@@ -82488,7 +82482,7 @@ S SPACER STRIKE TT U -->

<!-- XXX check that #refsRFC([0-9]+) is always for [RFC\1] -->

<!--
<!-- REFS

[COMPUTABLE] On computable numbers, with an application to the
Entscheidungsproblem. Alan M. Turing. In Proceedings of the London
@@ -82502,6 +82496,8 @@ S SPACER STRIKE TT U -->

[UNICODECASE] Unicode Standard Annex #21, Case Mappings

[UTS22] http://unicode.org/reports/tr22/#Charset_Alias_Matching

-->


0 comments on commit dfa984f

Please sign in to comment.