This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Try this page: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.venere.com%2Fit%2Fsitemap% 2Findex.php then click che XHTML validation at bottom of the page. The page wouldn't validate because of character encoding problem. If I manually select a character encoding that validator would accept (iso), the page doesn't validate as xhtml 1.0.
results invalid because of <strong>...</strong> marking the position of the error cutting in the middle of a unicode char. *** This bug has been marked as a duplicate of 921 ***
Now the validator says: Sorry, I am unable to validate this document because on lines 523, 537, 544, 558, 565, 579, 586, 600, 621, 628, 649 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication. and now I much much slower to load the page! (before was almost immediately)
Yes, the validator says there are encoding errors, and that's precisely what bug 921 is about, so we will track this issue in bug 921. Please do not reopen this issue unless you have proof that the two issues are different. Thanks. *** This bug has been marked as a duplicate of 921 ***