diff --git a/encoding.bs b/encoding.bs index ae966cd..dd4a25d 100644 --- a/encoding.bs +++ b/encoding.bs @@ -1299,7 +1299,7 @@ interface mixin TextDecoderCommon {

  1. Set decoder's BOM seen to true. -

  2. If item is U+FEFF, then continue. +

  3. If item is U+FEFF BOM, then continue.

  • Append item to output. @@ -1607,7 +1607,8 @@ method steps are: written is greater than or equal to the number of bytes in result, then:

      -

    1. If item is greater than U+FFFF, then increment read by 2. +

    2. If item's value is greater than 0xFFFF, then + increment read by 2.

    3. Otherwise, increment read by 1. @@ -1915,7 +1916,7 @@ constructor steps are:

      {{DOMString}}, as well as an I/O queue of code units rather than scalar values, are used here so that a surrogate pair that is split between chunks can be reassembled into the appropriate scalar value. The behavior is otherwise identical to {{USVString}}. In particular, - lone surrogates will be replaced with U+FFFD. + lone surrogates will be replaced with U+FFFD (�).

    4. Let output be the I/O queue of bytes « end-of-queue ». @@ -1973,13 +1974,13 @@ constructor steps are:

    5. Prepend item to input. -

    6. Return U+FFFD. +

    7. Return U+FFFD (�).

  • If item is in the range U+D800 to U+DBFF, inclusive, then set pending high surrogate to item and return continue. -

  • If item is in the range U+DC00 to U+DFFF, inclusive, then return U+FFFD. +

  • If item is in the range U+DC00 to U+DFFF, inclusive, then return U+FFFD (�).

  • Return item. @@ -2390,10 +2391,10 @@ consumers of content generated with GBK's encoder.

  • Return error. -

  • If byte is an ASCII byte, return - a code point whose value is byte. +

  • If byte is an ASCII byte, then return a code point whose + value is byte. -

  • If byte is 0x80, return code point U+20AC. +

  • If byte is 0x80, then return U+20AC (€).

  • If byte is in the range 0x81 to 0xFE, inclusive, set gb18030 first to byte and return continue. @@ -3345,13 +3346,15 @@ https://stackoverflow.com/questions/6986789/why-are-some-bytes-prefixed-with-0xf ioQueue and byte, runs these steps:

      -

    1. If byte is end-of-queue, return - finished. +

    2. If byte is end-of-queue, then return finished. -

    3. If byte is an ASCII byte, return - a code point whose value is byte. +

    4. Let byteValue be byte's value. -

    5. Return a code point whose value is 0xF780 + byte − 0x80. +

    6. If byte is an ASCII byte, then return a code point whose + value is byteValue. + +

    7. Return a code point whose value is + 0xF780 + byteValue − 0x80.

    @@ -3361,14 +3364,15 @@ https://stackoverflow.com/questions/6986789/why-are-some-bytes-prefixed-with-0xf ioQueue and code point, runs these steps:
      -

    1. If code point is end-of-queue, return - finished. +

    2. If code point is end-of-queue, then return finished. -

    3. If code point is an ASCII code point, return - a byte whose value is code point. +

    4. Let codePointValue be code point's value. + +

    5. If code point is an ASCII code point, then return a byte whose + value is codePointValue. -

    6. If code point is in the range U+F780 to U+F7FF, inclusive, return - a byte whose value is code point − 0xF780 + 0x80. +

    7. If codePointValue is in the range 0xF780 to 0xF7FF, inclusive, then return a + byte whose value is codePointValue − 0xF780 + 0x80.

    8. Return error with code point.