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 298 - Context sensitive tips for DOCTYPE/Charset...
Summary: Context sensitive tips for DOCTYPE/Charset...
Status: NEW
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.6.1
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: Terje Bless
QA Contact: qa-dev tracking
Depends on:
Reported: 2003-08-27 00:38 UTC by Terje Bless
Modified: 2007-03-29 18:49 UTC (History)
0 users

See Also:


Description Terje Bless 2003-08-27 00:38:08 UTC
From Håvard Tveite <>:

When a user has chosen "Encoding" and "Doctype" on the
validator page, it would be very useful if the validator
could make a suggestion regarding the use of tags.

For instance when choosing "iso-8859-1 (Western Europe)" for
Encoding and "HTML 2.0" for Doctype, the Validator currently
gives the following information:

 >DOCTYPE Override in effect! Any DOCTYPE Declaration in the document
 >has been suppressed and the DOCTYPE for «HTML 2.0» inserted instead.
 >The document will not be Valid until you alter the source file to
 >reflect this new DOCTYPE.

If, in addition, something like the following could be
suggested to the user, I think it would help beginners a lot:

  You can specify that this page uses the DOCTYPE "HTML 2.0"
  by inserting:
  as the first line of the document.
  You can specify that the character encoding is "iso-8859-1"
  by inserting:
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  within the <head> tag of the document.

I hope it is possible to make this information available in
standard mode (if that is not possible, perhaps it culd be
available in verbose mode).
Comment 1 Terje Bless 2003-08-27 00:39:34 UTC
With the infrastructure for better handling of DCOTYPEs in 0.7.0, we should be
able to add this with a fairly simple lookup table (which we'll allready have.
Comment 2 rtbeauregard 2004-06-24 10:28:32 UTC
Not sure if this is the best place to post this...
Recently I discovered that using a doctype without a url, for example, <!DOCTYPE HTML PUBLIC "-//
W3C//DTD HTML 4.01 Transitional//EN"> instead of, <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 
4.01 Transitional//EN"  ""> produces different results in 
different browsers.  It would be nice if the validator suggested, at the top of the validation results, to 
add the url to the doctype.
Thanks for your attention - apologies if this is an irrelevant post.
Comment 3 Terje Bless 2004-09-01 12:56:18 UTC
Accepting buig and targetting 0.7.0 release. May have to bump for a later
version because it involves some tedious work and timing issues may get in
the way.
Comment 4 Terje Bless 2004-09-09 18:30:17 UTC
Don't see this happening for 0.7.0; retargetting and removing blocker.