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 2572 - when no character encoding found, fatal_byte_error should also output charset warning
Summary: when no character encoding found, fatal_byte_error should also output charset...
Status: RESOLVED FIXED
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.1
Hardware: All All
: P2 normal
Target Milestone: 0.8.0
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-09 05:04 UTC by Olivier Thereaux
Modified: 2007-05-07 16:23 UTC (History)
0 users

See Also:


Attachments

Description Olivier Thereaux 2005-12-09 05:04:15 UTC
In case no character encoding info can be found through the usual algorithms, the validator outputs a 
warning about that missing info, e.g:
http://validator.w3.org/check?uri=http%3A%2F%2Fqa-dev.w3.org%2Fwmvs%2FHEAD%2Fdev%2Ftests%
2Fnocharset.html&charset=%28detect+automatically%29

However, if the document has bytes that cannot be mapped as utf-8 (or whatever fallback charset), the 
fatal error message (fatal_byte_error) alone is given, without the usual warning about lack of encoding, 
which can be confusing, e.g:

http://validator.w3.org/check?uri=http://qa-dev.w3.org/wmvs/HEAD/dev/tests/
nocharset_notutf8.html;ss
Comment 1 Olivier Thereaux 2007-05-07 16:12:11 UTC
looking into this now
Comment 2 Olivier Thereaux 2007-05-07 16:23:35 UTC
Done in CVS.