749 2004-05-27 20:04:07 +0000 Fatal errors trigger XHTML output for XML output method 2005-02-04 19:46:06 +0000 1 1 1 Unclassified Validator check 0.7.0 Other other RESOLVED FIXED http://validator.w3.org/check?uri=http://www.w3.org/robots.txt;output=xml P2 normal 0.7.0 856 1 bjoern link www-validator-cvs oldest_to_newest 1954 0 bjoern 2004-05-27 20:04:08 +0000 E.g. http://validator.w3.org/check?uri=http://www.w3.org/robots.txt;output=xml in case of fatal errors such as an illegal mime type the validator returns an XHTML document even for the XML output method. It should return this information encoded in the XML format. 2534 1 ville.skytta 2004-10-16 22:14:52 +0000 Hm, I guess we should templatize the XML (and EARL and n3) outputs too. The current dir structure doesn't provide a separate dir for these, should it? Alternatively, we could do $template.{xml,earl,n3}.tmpl or something like that. While at it, perhaps it would be a good idea to switch to RFC3066 formatted language identifiers (en-us and friends) in language specific dir names to avoid unnecessary mappings to the Unixish (?) (en_US and friends) ones? 4219 2 link 2005-02-04 19:46:06 +0000 Fixed. Fatal errors now output the correct format, noting the fatal error, and refers to interactive mode in the web interface to determine the exact nature of the problem (to avoid arbitrary HTML in the XML output, e.g.).