W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2010

[Bug 10890] i18n comment : Allow utf-16 meta encoding declarations

From: <bugzilla@jessica.w3.org>
Date: Fri, 01 Oct 2010 07:18:39 +0000
To: public-i18n-core@w3.org
Message-Id: <E1P1Zt9-0007fC-5G@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10890

Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsivonen@iki.fi

--- Comment #1 from Henri Sivonen <hsivonen@iki.fi> 2010-10-01 07:18:38 UTC ---
I'm strongly opposed to ever making <meta charset="utf-16"> conforming.

When the file is actually encoded in UTF-16, <meta charset="utf-16"> has no
effect. If authors think it has an effect, the mental model the authors have of
how character decoding works is severely faulty and failing to notify authors
of the faulty mental model will lead to the authors acting on the faulty model
and shooting themselves or their users in the foot later.

When the file is not actually encoded in UTF-16, <meta charset="utf-16"> means
the same as <meta charset="utf-8"> and is a clear authoring error. It would be
completely illogical not to flag it as an error. That Web compat requires this
UA behavior is evidence of authors getting things wrong when they try to use
<meta charset="utf-16">.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You reported the bug.
Received on Friday, 1 October 2010 07:18:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 1 October 2010 07:18:43 GMT