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

[Bug 24336] New: Encoding names should match what people actually call them

From: <bugzilla@jessica.w3.org>
Date: Mon, 20 Jan 2014 18:18:42 +0000
To: www-international@w3.org
Message-ID: <bug-24336-4285@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24336

            Bug ID: 24336
           Summary: Encoding names should match what people actually call
                    them
           Product: WHATWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Encoding
          Assignee: annevk@annevk.nl
          Reporter: geoffers+w3cbugs@gmail.com
        QA Contact: sideshowbarker+encodingspec@gmail.com
                CC: mike@w3.org, www-international@w3.org

http://gsnedders.html5.org/web-encoding-names/results.html shows what
document.characterSet returns in current versions of browsers. Notably, Firefox
and Chrome both return the uppercased names for many of these. (IE returns them
all lowercase except "GB18030"; ZombieOpera returns them all lowercase)

Googling these encoding names it becomes clear that almost everyone refers to
"UTF-8", "ISO-8859-n", etc. (uppercased), and as there is no interop here
currently, and the proposed behaviour matches Firefox/Chrome, it would seem
better to just give them their names that are in common usage.

As such, I propose to change the names to the following (thereby changing case
only):

 - UTF-8
 - IBM866
 - ISO-8859-n
 - ISO-8859-8-I
 - KOI8-R
 - KOI8-U
 - HZ-GB-2312
 - Big5
 - EUC-JP
 - ISO-2022-JP
 - Shift_JIS
 - EUC-KR
 - UTF-16BE
 - UTF-16LE

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 20 January 2014 18:18:44 UTC

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