This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16686 - euc-kr lead byte range
Summary: euc-kr lead byte range
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Encoding (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+encodingspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-10 16:27 UTC by Anne
Modified: 2012-10-30 17:13 UTC (History)
2 users (show)

See Also:

Attachments

Description Anne 2012-04-10 16:27:57 UTC 
-- 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).
Comment 1 Anne 2012-04-16 16:39:00 UTC 
The difference would be that 0xFE and a valid trail byte would be replaced by U+FFFD rather than just 0xFE.
Comment 2 pub-w3 2012-04-25 16:37:03 UTC 
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.