[e] (0) Spork means that the W3C actually have a real list of deltas …

…between this version and their version now.

Affected topics: HTML

git-svn-id: https://svn.whatwg.org/webapps@8890 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

  specification index</a>.</p>

  <p class=note>Although we have asked them to stop doing so, the W3C also republishes some parts
  of this specification as separate documents. There are numerous differences between this
  specification and the W3C forks; some minor, some major. Unfortunately these are not currently
  accurately documented anywhere, so there is no way to know which are intentional and which are
  not.</p>
  of this specification as separate documents.</p>


  <h3 id=background>1.3 Background</h3>
  new features as needed to evolve the platform.</p>

  <p>Since then, the WHATWG has been working on this specification (amongst others), and the W3C has
  been copying fixes made by the WHATWG into their fork of the document, as well as making other
  changes, some intentional and some not, with no documentation listing or explaining the
  differences.</p>
  been copying fixes made by the WHATWG into their fork of the document (which also has other
  changes).</p>



  <code id=changing-the-encoding-while-parsing:the-meta-element><a href=#the-meta-element>meta</a></code> element.</p> 


  <h5 id=preprocessing-the-input-stream>12.2.2.5 Preprocessing the input stream</h5><div class=status><input onclick=toggleStatus(this) value=⋰ type=button><p class=bugs><strong>Spec bugs:</strong> <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27413" title="As I read this, CR LF LF LF should be replaced by LF. Surely we just mean to replace CR LF as LF?">27413</a></div>
  <h5 id=preprocessing-the-input-stream>12.2.2.5 Preprocessing the input stream</h5>

  <p>The <dfn id=input-stream>input stream</dfn> consists of the characters pushed into it as the <a href=#the-input-byte-stream id=preprocessing-the-input-stream:the-input-byte-stream>input byte
  stream</a> is decoded or from the various APIs that directly manipulate the input stream.</p>

index

  specification index</a>.</p>

  <p class=note>Although we have asked them to stop doing so, the W3C also republishes some parts
  of this specification as separate documents. There are numerous differences between this
  specification and the W3C forks; some minor, some major. Unfortunately these are not currently
  accurately documented anywhere, so there is no way to know which are intentional and which are
  not.</p>
  of this specification as separate documents.</p>


  <h3 id=background>1.3 Background</h3>
  new features as needed to evolve the platform.</p>

  <p>Since then, the WHATWG has been working on this specification (amongst others), and the W3C has
  been copying fixes made by the WHATWG into their fork of the document, as well as making other
  changes, some intentional and some not, with no documentation listing or explaining the
  differences.</p>
  been copying fixes made by the WHATWG into their fork of the document (which also has other
  changes).</p>



  <code id=changing-the-encoding-while-parsing:the-meta-element><a href=#the-meta-element>meta</a></code> element.</p> 


  <h5 id=preprocessing-the-input-stream>12.2.2.5 Preprocessing the input stream</h5><div class=status><input onclick=toggleStatus(this) value=⋰ type=button><p class=bugs><strong>Spec bugs:</strong> <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27413" title="As I read this, CR LF LF LF should be replaced by LF. Surely we just mean to replace CR LF as LF?">27413</a></div>
  <h5 id=preprocessing-the-input-stream>12.2.2.5 Preprocessing the input stream</h5>

  <p>The <dfn id=input-stream>input stream</dfn> consists of the characters pushed into it as the <a href=#the-input-byte-stream id=preprocessing-the-input-stream:the-input-byte-stream>input byte
  stream</a> is decoded or from the various APIs that directly manipulate the input stream.</p>

source

  specification index</a>.</p>

  <p class="note">Although we have asked them to stop doing so, the W3C also republishes some parts
  of this specification as separate documents. There are numerous differences between this
  specification and the W3C forks; some minor, some major. Unfortunately these are not currently
  accurately documented anywhere, so there is no way to know which are intentional and which are
  not.</p>
  of this specification as separate documents.</p>


  <h3>Background</h3>
  new features as needed to evolve the platform.</p>

  <p>Since then, the WHATWG has been working on this specification (amongst others), and the W3C has
  been copying fixes made by the WHATWG into their fork of the document, as well as making other
  changes, some intentional and some not, with no documentation listing or explaining the
  differences.</p>
  been copying fixes made by the WHATWG into their fork of the document (which also has other
  changes).</p>