- From: <bugzilla@jessica.w3.org>
- Date: Tue, 01 Jul 2014 15:22:13 +0000
- To: www-international@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23646 --- Comment #42 from Paul Eggert <eggert@cs.ucla.edu> --- > You should be doing your Web compat reasoning from browsers with substantial market share. eww isn't one. Well, I happened to be using Emacs at the time, but how about Chromium and Firefox? Please see <http://cs.ucla.edu/~eggert/tz/text.html>: it is labeled as charset=US-ASCII but actually encoded in UTF-8 with some non-ASCII characters. Firefox 30.0 and Chromium 34.0.1847.116 both behave like Emacs eww, and decode it as UTF-8. Again, I propose that the standard be changed to allow decoders to treat UTF-8 properly even if it's mislabeled as US-ASCII, since that's what browsers actually do in some cases, and it's helpful behavior that should not be prohibited. The argument that the behavior is "bad for interoperability" a weak one: for a user, seeing text is more interoperable than seeing mojibake. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Tuesday, 1 July 2014 15:22:15 UTC