16686 2012-04-10 16:27:57 +0000 euc-kr lead byte range 2012-10-30 17:13:08 +0000 1 1 1 Unclassified WHATWG Encoding unspecified PC All RESOLVED FIXED P2 normal Unsorted 1 annevk annevk mike pub-w3 sideshowbarker+encodingspec oldest_to_newest 66572 0 annevk 2012-04-10 16:27:57 +0000 -- 5.2 and 7: 0xFD probably ought to be 0xFE to reflect EUC (even though Row 94 in KS X 1001 happens to be empty). 66745 1 annevk 2012-04-16 16:39:00 +0000 The difference would be that 0xFE and a valid trail byte would be replaced by U+FFFD rather than just 0xFE. 67028 2 pub-w3 2012-04-25 16:37:03 +0000 FD A1 FE A1 FD A1 is decoded as 爻�爻 (modulo PUA v. U+FFFD) in IE6, Opera and Safari. Reprocessing A1 as a lead byte instead gives 爻�∨� (A1 FD encodes ∨). Firefox actually does this, but this approach seems likely to break more than it fixes. 67042 3 annevk 2012-04-25 18:54:18 +0000 http://dvcs.w3.org/hg/encoding/rev/1e1c81cfd07d