W3C home > Mailing lists > Public > www-international@w3.org > October to December 2014

[Bug 27675] New: U+FFFD in euc_kr index

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Dec 2014 16:49:47 +0000
To: www-international@w3.org
Message-ID: <bug-27675-4285@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27675

            Bug ID: 27675
           Summary: U+FFFD in euc_kr index
           Product: WHATWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Encoding
          Assignee: annevk@annevk.nl
          Reporter: public+w3@mearie.org
        QA Contact: sideshowbarker+encodingspec@gmail.com
                CC: mike@w3.org, www-international@w3.org

The updated euc_kr table now has the following entries:

---8<---
 5916    0xFFFD    � (REPLACEMENT CHARACTER)
 5917    0xFFFD    � (REPLACEMENT CHARACTER)
 5918    0xFFFD    � (REPLACEMENT CHARACTER)
 5919    0xFFFD    � (REPLACEMENT CHARACTER)
 5920    0xFFFD    � (REPLACEMENT CHARACTER)
 5921    0xFFFD    � (REPLACEMENT CHARACTER)
[snip]
 5948    0xFFFD    � (REPLACEMENT CHARACTER)
 5949    0xFFFD    � (REPLACEMENT CHARACTER)
 5950    0xFFFD    � (REPLACEMENT CHARACTER)
 5951    0xFFFD    � (REPLACEMENT CHARACTER)
 5952    0xFFFD    � (REPLACEMENT CHARACTER)
 5953    0xFFFD    � (REPLACEMENT CHARACTER)
---8<---

They correspond to byte sequences A0 5B..60 and A0 7B..80, which are gaps
between UHC ranges. I don't think Bug 16691 intended this (as they are the only
occurrences of U+FFFD throughout the indices at the moment). This causes an
otherwise valid decoder to accept those sequences even when the fatal mode is
in the use.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 19 December 2014 16:49:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:38 UTC