W3C home > Mailing lists > Public > www-amaya@w3.org > July to September 2003

Re: parsing issues with amaya 8.1b

From: Irene Vatton <irene.vatton@inrialpes.fr>
Date: Thu, 4 Sep 2003 16:32:51 +0200
To: "John Russell" <ve3ll@rac.ca>
Cc: www-amaya@w3.org
Message-Id: <20030904163251.1d0edad1.irene.vatton@inrialpes.fr>

On Thu,  4 Sep 2003 08:14:49 -0400 (EDT)
"John Russell" <ve3ll@rac.ca> wrote:

> One of my common uses of amaya is to verify students
> documents quickly. amaya catches a few problems that
> the w3 and wdg parsers miss. I really like that.   However 
> I am now seeing a couple of badly formed documents 
> (according to w3.org and wdg)  that amaya does not raise
> alarms on ....  one is invalid characters and another is on
>  invalid nesting. the two test files are included. 
> Are these things Amaya  should flag?
> Are they now on the 2.do list? --
> john russell ve3ll@rac.ca [those are L's as in LLAMA]
> http://home.cogeco.ca/~ve3ll
> http://home.cogeco.ca/~trains
> http://home.cogeco.ca/~cipher

We did that at the beginning, but we abandonned the idea to do a too
strict control on loaded documents.
We let that role to validators.
Today, Amaya does a minimum of control on loaded documents:
  + it checks that they are well-formed (if it's a XHTML document)
  + it fixes a set of important errors (misplaced end tags, <td> outside a <table>
  + it detects the use of invalid or unknown tags.
But new created documents with Amaya are valid, and it only allows the user to
add new elements at a valid position.

I agree with you, we probably have to flag invalid characters.
Irène Vatton                     INRIA Rhône-Alpes
INRIA                               ZIRST
e-mail: Irene.Vatton@inria.fr       655 avenue de l'Europe
Tel.: +33 4 76 61 53 61             Montbonnot
Fax:  +33 4 76 61 52 07             38334 Saint Ismier Cedex - France
Received on Thursday, 4 September 2003 10:35:15 UTC

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