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

[Bug 23650] Consider making the label for utf-8 "UTF-8"

From: <bugzilla@jessica.w3.org>
Date: Mon, 28 Oct 2013 01:56:41 +0000
To: www-international@w3.org
Message-ID: <bug-23650-4285-6RENW30VEE@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23650

Martin Dürst <duerst@it.aoyama.ac.jp> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |duerst@it.aoyama.ac.jp

--- Comment #1 from Martin Dürst <duerst@it.aoyama.ac.jp> ---
Charset/encoding labels are case-insensitive all over the Internet, so with
respect to functionality, this shouldn't matter at all. And the spec explicitly
says so, please look for
http://encoding.spec.whatwg.org/#ascii-case-insensitive.

If it makes a difference, then something somewhere (browser or server or other)
is broken, and should be fixed. If this is indeed the case, it would be good to
have examples.

As for whether the spec should use 'utf-8' or 'UTF-8', I personally would
prefer 'UTF-8', because being an acronym, that's how it's written in books and
other documentation. But looking at the spec, that would mean that many other
labels (starting with US-ASCII and ISO-8859-1) would have to be upper-cased,
too.

As this is a purely editorial issue, we can leave that to the editor. An
alternative is to provide a pull request.

What I'd like to avoid is to change the case of the file names for the data
files for the encodings. Software that handles that may not do case-insensitive
there. (But if we change these too, that's not the end of the world either.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 28 October 2013 01:56:42 UTC

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