5 ms·
It's not just you, Firefox auto detects the encoding as Western, if you set it to Unicode manually it works.
by yaph 12y ago
It's not just you, Firefox auto detects the encoding as Western, if you set it to Unicode manually it works.
- Dorian-Marie 12y agoSomeone needs a <meta charset="utf-8">
- masklinn 12y agoMostly someone needs to set the useful headers correctly instead of sending pointless garbage.
- teach 12y agoI wish you had said this differently. Not only is it hostile, it doesn't contain enough information. I run a web site. All my pages contain <meta charset='utf-8'> in the title. What are you suggesting I do differently?
- voidlogic 12y agoHe probably meant HTTP header: Ex: Content-Type: text/html; charset=UTF-8
- timClicks 12y agoHTTP has good support for declaring content encoding. Putting this in HTML probably seems like wasted bytes to protocol purists.
- andyroid 12y agoOne advantage of putting it in a meta tag is that the encoding is preserved even if the document is read from elsewhere (parsed from the local filesystem, etc).
- vardump 12y agoNot to mention that not everyone has control over what HTTP headers get sent. It's way easier for a non-technical person to just add it in meta tag. Definitely a lot better option than leaving the matter to browser encoding sniffer!
- tragic 12y agoYeah, Chrome's auto-detect sorts it out. Weirdly it's inconsistent (chapter 6 has the meta charset tag in there). Bit entry level so far, even for a moron like me, but enjoying it.