This is a bug report for the record. I used "Validate by Direct Input" today. I got the message: No Character Encoding Found! Falling back to UTF-8. Given that the validation form is UTF-8, every reasonable browser will actually send data to the server in UTF-8. The result of that message is therefore correct, but the message shouldn't be there. Even more to the point, providing a charset in a <meta> element validates correctly, but produces garbage. Try putting the following into the form (short, but actually valid): -------- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <title>Hello World!</title> <meta http-equiv='Content-Type' content='text/html; charset=shift_jis'><p>今 日は、世界! -------- This validates, but the Japanese text turns into garbage. The right thing here is to produce a message such as: "Encoding declared is shift_jis, but validating as UTF-8 because uploaded as UTF-8." (and then actually do that) Regards, Martin.Received on Friday, 2 September 2005 23:05:35 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:58:53 UTC