|
REPORT COPYRIGHT VIOLATION IN REPLY
|
|
Message Subject
|
the newtown bee, newtown's local paper has been hacked by han chinese language! word "shooting" "enemy" "evil force"
|
|
Poster Handle
|
Anonymous Coward |
|
Post Content
|
I figured it out. They have a bug in their code. At the very top, <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> Take a look here... [ link to www.w3schools.com] This isn't valid HTML, they are missing double quotes around text/html and utf-8, so internet explorer, chrome etc... are unable to figure out what encoding to use, and by default are selecting unicode UTF-16LE That is not the same as Unicode UTF-8, which it should be. Try it out in Chrome, go to the page, then click Tools -> Encoding, you will see utf16 is set, now click utf8 nd it will look normal, then select utf16 again. Still strange this would happen tonight. (Yes i'm a programmer) Not to argue the point, but that's valid code for HTML 4.01 and that's what their DOCTYPE declares: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" From the w3schools site page you referenced, and where I learned to write XHTML: Differences Between HTML 4.01 and HTML5 The scheme attribute is not supported in HTML5. HTML5 has a new attribute, charset, which makes it easier to define charset: HTML 4.01: <meta http-equiv="content-type" content="text/html; charset=UTF-8"> HTML5: <meta charset="UTF-8"> If you notice the double quotes are the same in both. I ran their sire through the W3C Markup Validation Service and it doesn't check as valid HTML 4.01 Strict but that isn't listed as one of the reasons why. Not in STRICT mode it isn't, which they have declared it to be with this line... <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" " [ link to www.w3.org] You can validate it your self here... [ link to validator.w3.org] NEEEERRRD!!!!!!  I actually stand corrected, after thinking it over for a few minutes... (im not a web programmer so html is not something I know off the top of my head) I realize the error now is actually this... The HTML code is stating it's UTF-8, which is correct, but the SERVER is responding to requests of the page by adding the UNICODE encoding, which conflicts with what the page is suppose to be... UNICODE isn't a real encoding, it's a character page, and so browsers are free to pick which ever UNICODE encoding they want, for IE and chrome its UTF-16 which is completly different then UTF-8 So it is indeed an server error, maybe someone really did hack them to make it display these weird characters.
|
|
|
Please verify you're human:
|
|
|
Reason for copyright violation:
|
