W3C home > Mailing lists > Public > www-international@w3.org > April to June 2014

[Bug 25266] Consider adding 34 code points to the EUC-JP decoder present in Blink/ICU's euc-jp-2007.

From: <bugzilla@jessica.w3.org>
Date: Mon, 28 Apr 2014 21:35:45 +0000
To: www-international@w3.org
Message-ID: <bug-25266-4285-mgMo6oUhPX@http.www.w3.org/Bugs/Public/>

Jungshik Shin <jshin@chromium.org> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #7 from Jungshik Shin <jshin@chromium.org> ---
>From bug 16141 : 
The ones that are still missing can be found in an IBM extension to JIS X 0212,
Rows 83--84.

However, if Firefox has never supported them [1], I'm not wed to them, either.
And I'll just get rid of them from Chromium's new euc-jp table. Then, it'll be
exactly the same as specified in the encoding spec. 

> I don't understand the requested 0xFC 0xFB mapping. Per the euc-jp decoder 
> algorithm that becomes 8644 as pointer, which maps to U+FFE2 in index jis0208.

You're right. It's there. Sorry about the noise on this code point. 

I'm closing this as wontfix.  

[1] The Chrome's current table (not the one I'm adding based on the encoding
spec but the one that is currently used in released versions) was made by
comparing IE, Firefox and ICU tables, but lost is how exactly I 'curated' and
'merged' them.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 28 April 2014 21:35:46 UTC

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