16687 2012-04-10 16:28:56 +0000 iso-2022-kr decoder feedback 2013-08-23 10:36:01 +0000 1 1 1 Unclassified WHATWG Encoding unspecified PC Windows 3.1 RESOLVED INVALID P2 normal Unsorted 20599 1 annevk annevk mike pub-w3 sideshowbarker+encodingspec oldest_to_newest 66573 0 annevk 2012-04-10 16:28:56 +0000 Are you sure \n (0x1A) should switch to ASCII? (Same comment as for ISO-2022-JP.) 67353 1 pub-w3 2012-05-06 13:28:44 +0000 The following illustrates a number of ISO-2022-KR encoding errors: <p>Space (' ') between two-byte sequences: \x0EVP VPVP VPVP VP\x0F <p>Newline ('\\n') between two-byte sequences: \x0EVP\nVPVP\n\nVPVP\nVP\x0F <p>Space (' ') inside two-byte sequences: \x0EVPV PVP VPVP\x0F <p>Newline ('\\n') inside two-byte sequences: \x0EVPV\nPVP\nVPVP\x0F <p>Aligned escape sequence: \x0EVPVP\x1B\$)CVP\x0F <p>Misaligned escape sequence: \x0EVPV\x1B\$)CPVP\x0F <p>Aligned shift in: \x0EVPVP\x0FVP\x0F <p>Misaligned shift in: \x0EVPV\x0FPVP\x0F <p>Aligned shift out: \x0EVPVP\x0EVP\x0F <p>Misaligned shift out: \x0EVPV\x0EPVP\x0F <p>Incomplete escape sequence: VP\x1BVP\x1B\$VP\x1B\$)VP\x1B\$)CVP <p>Aligned incomplete escape sequence: \x0EVPVP\x1B\$VPVP\x0F <p>Misaligned incomplete escape sequence: \x0EVPV\x1B\$PVPVP\x0F Testing in IE (no differences between IE6 and IE9), Opera, Safari and Firefox gives the following results: Only Opera gets out of synch when a space appears between two-byte sequences. Firefox and Opera do switch to ASCII when a newline is found in two-byte mode. IE and Safari however remain in two-byte mode, and they have the same error handling. All browsers recognise a misaligned shift-in (i.e., 0F as a trail byte in two-byte mode as a way of switching to one-byte mode). The only divergence is that IE eats the following byte. A misaligned shift-out or a misaligned escape sequence (ESC '$' ')' 'D') is ignored by IE. Other browsers misalign/realign. An incomplete escape sequence in ASCII mode is converted to characters byte by byte in IE and Firefox, starting with an escape character, and with no U+FFFD being inserted. Perhaps this should not be an error at all. An incomplete escape sequence in 2-byte mode makes Opera switch to ASCII mode. All other browsers stay in 2-byte mode and have essentially the same error handling (at least for the example above). 67354 2 pub-w3 2012-05-06 13:31:04 +0000 Typo: the escape sequence is ESC '$' ')' 'C'. 92498 3 annevk 2013-08-23 10:36:01 +0000 This is obsolete now.