This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1488 - Validator results doesn't validate as XHTML
Summary: Validator results doesn't validate as XHTML
Status: RESOLVED DUPLICATE of bug 921
Alias: None
Product: Validator
Classification: Unclassified
Component: Parser (show other bugs)
Version: 0.7.0
Hardware: PC Windows XP
: P2 trivial
Target Milestone: ---
Assignee: Terje Bless
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-30 18:16 UTC by Marco Marsala
Modified: 2005-06-02 22:48 UTC (History)
0 users

See Also:


Attachments

Description Marco Marsala 2005-05-30 18:16:55 UTC
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.
Comment 1 Olivier Thereaux 2005-06-02 06:14:01 UTC
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 ***
Comment 2 Marco Marsala 2005-06-02 12:57:09 UTC
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)
Comment 3 Olivier Thereaux 2005-06-02 22:48:12 UTC
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 ***