Re:UTF-8 Everywhere (2012)
by tajen on Sunday June 19, 2016 @05:04PM
(#11934666)
I'm on Mac and I've had problems with Chrome sending ajax requests or decoding ajax responses in ISO-8859-1, if I remember well. I had to add "; charset=utf-8" to my headers. I remember it was a browser problem, and I think it was the same for all browsers.
[ Parent
| on HN ]
Re:UTF-8 Everywhere (2012)
by TazeTSchnitzel on Sunday June 19, 2016 @05:09PM
(#11934684)
For backwards-compatibility's sake, where a web page doesn't specify a character set, browsers will assume the predominant pre-Unicode encoding used in your region.
Re:UTF-8 Everywhere (2012)
by scrollaway on Sunday June 19, 2016 @10:03PM
(#11935692)
Why is this still the case? UTF8 is dominant now, wouldn't it make more sense to assume UTF8?
The older the site, the less likely it is that it will have been updated. Therefore, it's reasonable to assume that newer sites will either declare UTF-8, or can be modified to declare UTF-8, while old sites stay the way they always were, pre-UTF-8.
Keeping the backwards-compatibility heuristic the same makes sense.
Re:UTF-8 Everywhere (2012)
by TazeTSchnitzel on Tuesday June 21, 2016 @07:37AM
(#11944962)
Old sites lacked encoding declarations, and old browsers (e.g. early versions of IE) didn't support them.
Sites that want UTF-8 can ask for it.