Hello, Part of my hacking last week on the markup validator involved setting up "fuzzy matching" of unknown elements/attributes in order to have the validator say: “Line 12, Column 14: there is no attribute "crass". Maybe you meant "class" or "classid"?” The code is ready for testing on our development instance: http://qa-dev.w3.org/wmvs/HEAD/ … and I made a little writeup about the ideas and implementation details http://www.w3.org/blog/systeam/2009/02/16/validator_fuzzy_match Teaser: did you know that errors about unknown attributes/elements (either because of typo, case or simply non standard elt/attr) is by far the most common type of errors reported by the Markup Validator? Comments and thoughts welcome here, or on the systeam blog. In particular: * What do you think of this feature? Would you have implemented it differently? * Any suggestion for a better way to word/present the suggested correction for unknown element/attributes? * Any thought on other small improvements to the validator which would dramatically improve its usability? Thanks, olivier -- olivier Thereaux - W3C Open Source Software : http://www.w3.org/Status Do you ♥ Validators? Donate or become a Sponsor: http://www.w3.org/QA/Tools/DonateReceived on Monday, 16 February 2009 18:11:46 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 1 October 2009 14:49:13 GMT