W3C home > Mailing lists > Public > www-international@w3.org > January to March 2015

[Bug 28156] Separate GBK and GB18030 even for decoding (toUnicode)

From: <bugzilla@jessica.w3.org>
Date: Thu, 12 Mar 2015 16:35:15 +0000
To: www-international@w3.org
Message-ID: <bug-28156-4285-ERWFuofrwy@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28156

--- Comment #2 from Henri Sivonen <hsivonen@hsivonen.fi> ---
(In reply to Jungshik Shin from comment #0)
> I'm raising this issue because 1) Blink, Webkit, Firefox (and I guess, IE,
> too) have treated two encodings separately 

Firefox no longer does, so going back to the old state would involve extra work
for us...

(In reply to Anne from comment #1)
> I would have expected that treating them identically for decoding saves you
> a decoding table. Or would you reuse that anyway?

FWIW, the old code in Firefox reused the reusable tables.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 12 March 2015 16:35:20 UTC

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