10076 2010-07-04 08:33:32 +0000 Improve error location info for XML, JSON etc outputs 2013-02-14 17:41:17 +0000 1 1 1 Unclassified Validator check 1.0 PC Linux NEW P2 normal --- 9933 1 ville.skytta dave.null lavacochesmadrid www-validator-cvs oldest_to_newest 36566 0 ville.skytta 2010-07-04 08:33:32 +0000 Bug 9933 takes care of this for HTML output, this is about doing it also in XML, JSON etc outputs. +++ This bug was initially created as a clone of Bug #9933 +++ The info given by validator about error locations should be improved as the errors may not occur in the doc to be validated, they may be elsewhere. For example validate the following XHTML MP 1.2 doc with xmllint (libxml): <!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.2//EN" "http://www.openmobilealliance.org/tech/DTD/xhtml-mobile12.dtd"> <html> <head> <title> Plain Text </title> </head> <body> <p> This is <br/> A simple sample of XHTML MP </p> <div style="text-align:right"> Hello, world </div> </body> </html> $ xmllint --noout --postvalid t.xhtml http://www.openmobilealliance.org/tech/DTD/xhtmlmp12-form-1.mod:18: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0x92 0x53 0x20 0x52 OR ITS AFFILIATES REGARDING ANY OF THE IPR�S REPRESENTED ON THE OMA ^ http://www.openmobilealliance.org/tech/DTD/xhtmlmp12-form-1.mod:69: parser warning : PEReference: %form.element; not found <![%form.element;[ ^ [...] $ HEAD http://www.openmobilealliance.org/tech/DTD/xhtmlmp12-form-1.mod 200 OK Date: Tue, 15 Jun 2010 16:37:46 GMT Accept-Ranges: bytes ETag: "4cbc61cb759c71:1f3d" Server: Microsoft-IIS/6.0 Content-Length: 9885 Content-Type: application/octet-stream Last-Modified: Mon, 26 Feb 2007 15:01:52 GMT Client-Date: Tue, 15 Jun 2010 16:37:47 GMT Client-Peer: 195.238.226.77:80 Client-Response-Num: 1 MicrosoftOfficeWebServer: 5.0_Pub X-Powered-By: ASP.NET