2131 2005-09-11 05:18:51 +0000 Fatal error handling for non-HTML output formats 2007-05-17 04:28:22 +0000 1 1 1 Unclassified Validator check HEAD PC All NEW http://validator.w3.org/check?uri=http://example.invalid&output=n3 P2 normal 1.0 1 bjoern ot www-validator-cvs oldest_to_newest 6071 0 bjoern 2005-09-11 05:18:51 +0000 http://validator.w3.org/check?uri=http://example.invalid&output=n3 "end of document in prolog" might not be the best way to handle this; HEAD inherits this problem from 0.7.x; I'm not sure though what should be done here, the non-HTML output modes are not really designed to handle this as yet. 6715 1 ot 2005-10-18 07:28:21 +0000 The XML (soon-to-be soap) output has "fault" messages for this exact purpose. Not sure about earl/n3. 14557 2 ot 2007-03-28 01:47:11 +0000 (In reply to comment #1) > The XML (soon-to-be soap) output has "fault" messages for this exact purpose. > Not sure about earl/n3. Earl output will be updated in the near future, with the update of the earl spec. Targeting a future release. 15102 3 ot 2007-05-17 04:28:22 +0000 Note on the issue: the brokenness mostly comes from sub abort_if_error_flagged() which does not take into account outputs other than html. The issue is somewhat alleviated for the soap output by a hack that passes all the File->{Templates}->{Error}->param()s to the SOAPFault template, but it would be good to rewrite this with a cleaner model where: * for all of validation parameters are passed to only two html::template objects (output and fatal error) - or only one. * at output time, the template is assigned to a specific output