W3C home > Mailing lists > Public > www-amaya@w3.org > October to December 2002

Re: Amaya parser misses badly formed code

From: Laurent Carcone <Laurent.Carcone@inrialpes.fr>
Date: Tue, 26 Nov 2002 10:04:14 +0100
To: "John Russell" <ve3ll@rac.ca>
Cc: www-amaya@w3.org
Message-Id: <20021126090414.80E9616D60@tux.inrialpes.fr>

> http://www.racersinfo.com/folders/safety/safeMain.htm
> illustrates a problem within the parser where badly formed
> html is not flagged as such .... it is basically
> a numbered list that was terminated with a typo ....
> ie 
> <ol>
> <li>foo</li>
> <li>bar></li>
> <ol>
> instead of closing with a </ol>........  
> Shouldn't the Amaya parser signal all errors or divergences 
> from the spec, even if it doesn't cause problems in rendering.
> This is in addition to the parser not warning about backslashes
> being the wrong separator in image file names although it 
> prevents the display of the image...  that is another parser 
> problem needing fixing ....  

Hello John,

Actually, Amaya uses 2 different parsers, one for HTML documents, another one 
from XML documents (XHTML, MathML, SVG, ...).
The HTML parser tries to correct the most common errors (like the missing and 
tags) otherwise, most of the document on the web wouldn't be rendered (as the 
document you mentionned).
The XML parser is more strict and points out each not well-formed document 
(according to the XML spec.)

Laurent Carcone
Received on Tuesday, 26 November 2002 04:04:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:30:39 UTC