4 ms·
The article has a serious character set issue. It contains stuff like "doesn’t" instead of "doesn't".
by vog 15y ago
The article has a serious character set issue. It contains stuff like "doesn’t" instead of "doesn't".
- Xurinos 15y agoYour browser -- and my browser -- did not autodetect the character encoding correctly. Switch to Unicode (UTF-8), and it should look fine. I used Firefox.
- EdiX 15y agoThe reason our browsers don't autodetect the character encoding as utf-8 is because that page doesn't say it's utf-8. In that case browsers are allowed to assume it's latin-1.
- graywh 15y agoActually, it did say. In line 1. <?xml version="1.0" encoding="utf-8" ?> Perhaps your browser and mine disagree on when that declaration is acceptable. For reference, http://www.w3.org/International/questions/qa-html-encoding-declarations http://www.w3.org/International/questions/qa-html-encoding-d...
- nbpoole 15y agoIf you want to get pedantic about it, the content is being served as text/html (as opposed to application/xhtml+xml) which means the XML declaration isn't valid.
- wnight 15y agoWell, I'd like to know why it doesn't work. If that's pedantic, so be it. Edit: I think people took this the wrong way. I mean it's not pedantic to find the real problem. We're all better off because the poster I'm responding to showed us the real problem.
- LukeShu 15y agoYou're browser's detecting it as ISO-8859-1, not UTF-8. Do something like "View->Character Encoding->UTF-8".