48 2002-10-27 09:12:21 +0000 "Override" to same DOCTYPE should not give a warning. 2005-05-11 09:02:55 +0000 1 1 1 Unclassified Validator check 0.6.0 All other RESOLVED FIXED http://validator.w3.org/check?uri=http://qa-dev.w3.org/wmvs/HEAD/dev/tests/xhtml1-strict.html;ss;doctype=XHTML+1.0+Strict P3 minor --- 43 1 link link www-validator-cvs oldest_to_newest 79 0 link 2002-10-27 09:12:21 +0000 Reported by Björn Höhrmann <derhoermi@gmx.net>: I tried to validate http://www.websitedev.de/xhtml/xhtml1/ as ISO-8859-1 encoded XHTML 1.0 Transitional document. The validator responds * DOCTYPE Override in effect! Any DOCTYPE Declaration in the document has been suppressed and the DOCTYPE for «XHTML 1.0 Transitional» inserted instead. The document will not be Valid until you alter the source file to reflect this new DOCTYPE. The document located at <URL:http://www.websitedev.de/xhtml/xhtml1/> would validate as XHTML 1.0 Strict if you updated it to match the Options used. I don't need to update the page, it validates. If selected document type and the document type given in the document match, the validator should not shout at me. 85 1 link 2002-10-27 10:27:00 +0000 This can't be done with the current code; we never have the DOCTYPE from the override ad the DOCTYPE found in the document in the same format (FPI vs. Version string vs. a complete DOCTYPE) and neither do we have a mapping table to deal with this. OTOH, sufficient metadata/mapping tables for this is one of the things scheduled for the new config file parser/format. Setting blocker on Bug #43. 86 2 link 2002-10-27 10:29:38 +0000 Setting target to 0.7.0. 259 3 link 2002-12-03 01:58:03 +0000 Remove blocker on Bug #4 and adding Bjoern to the CC list. 2520 4 link 2004-10-12 19:19:00 +0000 Won't make it for 0.7.0. 3944 5 ot 2005-03-24 09:03:31 +0000 (In reply to comment #4) > Won't make it for 0.7.0. Actually I think we had all the logic ready, albeit scattered in the code. Fixed in CVS. 3376 6 ot 2005-05-11 09:02:55 +0000 adding test case URI