- From: Laurent Carcone <laurent@w3.org>
- Date: Wed, 24 Jan 2007 11:19:00 +0100
- To: "Charles McCathieNevile" <chaals@opera.com>
- Cc: jeff.hunt@stagecoach.co.nz, www-amaya@w3.org
On Tue, 23 Jan 2007 15:34:34 -0500 "Charles McCathieNevile" <chaals@opera.com> wrote: > > On Tue, 23 Jan 2007 13:23:38 -0500, Laurent Carcone <laurent@w3.org> wrote: > > > Jeff Hunt <jeff.hunt@stagecoach.co.nz> wrote: > > >> I wonder if it is possible to design Amaya to automatically know which > >> attributes are acceptable (and by inference what are not) in some sort > >> of general file, before it begins other more specific validation checks. > > > > Amaya works with an external file at parsing that indicates which > > elements/attributes are allowed according to the doctype. > > There was an error in that file for the attribute 'alt' > > Hello Laurent! What is this file? Can I edit it, and test Amaya with new > attributes that I want to enable (or more restrictive profiles)? Hello Charles, In fact, this file is included in Amaya binary, if you want to modify it you need to get the sources of Amaya and make your own binary. It is called 'HTMLnames.h' and located in the repertory Amaya/amaya. There are some comments within the file and the structure of the table is defined in 'parser.h'. Each line refers to an element/attribute defined in the S schema (HTML.S). If you want to add some new ones, you need first to modify this schema (also the presentation schema HTMLP.P I guess). Hope this help Thanks, Laurent > > cheers > > Chaals > > -- > Charles McCathieNevile, Opera Software: Standards Group > hablo español - je parle français - jeg lærer norsk > chaals@opera.com Try Opera 9.1 http://opera.com > > > -- Laurent Carcone carcone@w3.org W3C/ERCIM +33 (0)4 76 61 52 67 INRIA Rhône-Alpes, 655 Avenue de l'Europe 38334 Saint Ismier Cedex - France
Received on Wednesday, 24 January 2007 10:10:32 UTC