301 2003-08-27 09:27:07 +0000 Errors in DTDs are not distinguished from errors in document 2008-06-23 17:37:29 +0000 1 1 1 Unclassified Validator check 0.6.1 All All NEW http://flat5th.homeip.net/weav/dtd/shipconf2.xml P2 normal --- 1 link link bryce2 www-validator-cvs oldest_to_newest 699 0 link 2003-08-27 09:27:07 +0000 As a workaround for a different bug ("characters larger than nnn not supported"), the validator supresses error messages related to errors in DTDs (actually it supresses messages from any other source than the document beeing checked). This leads to the fun situation where the Validator reports a page as invalid but doesn't give any actual error messages. The correct fix is to deal with the original problem and begin reporting all errors again. 1842 1 link 2004-05-16 06:18:56 +0000 Marking 0.7 to put back on the radar. 2362 2 nick 2004-09-20 20:54:59 +0000 The problem goes deeper than this. We can't report DTD errors without a change to output formats, but you knew that. But it's also a fix for *standard* DTDs that emit warnings, like W3C HTML 4.0. Reporting DTD errors starts to look a little like the difference between Page Valet and Code Valet. Different tools. So let this be a post-m12n goal. 4215 3 link 2005-02-04 17:06:01 +0000 Taking up Nick (and Björn's) suggestion and retargetting this for some point in the future. Fixing this will open up a can of worms I'm not sure we can close until well after M12N. 15902 4 ot 2007-07-23 06:06:19 +0000 In validator 0.8.0, errors in the DTD are reported, although all errors are reported as if pertaining to document validated. Changing bug summary from: Errors in DTDs are Not Reported To: Errors in DTDs are not distinguished from errors in document 20754 5 bryce2 2008-06-23 17:37:29 +0000 I see this also, with <!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.1//EN" "http://www.openmobilealliance.org/tech/DTD/xhtml-mobile11.dtd">