- From: Nick Kew <nick@webthing.com>
- Date: Fri, 16 Apr 2004 22:41:33 +0100 (BST)
- To: Terje Bless <link@pobox.com>
- Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, olivier Thereaux <ot@w3.org>, validators community <www-validator@w3.org>
On Fri, 16 Apr 2004, Terje Bless wrote: > Bjoern Hoehrmann <derhoermi@gmx.net> wrote: > > >A number of problems can be solved if the validator would report the > >current open element(s) > > This is certainly possible to do, but I don't know if it can be easily done in > a manner that is actually usefull. One problem I forsee is that the listing of > open elements will be distracting for a great many error messages, and > misleading for a few of the rest, leaving the net benefit from this rather > less than initially envisioned. > > If you want to take a stab at this, getting open elements information is a > simple commandline switch to onsgmls; and you'll need to modify the error > output parsing as well as the HTML display code to implement it. FWIW, Code Valet offers this option to users. But of course it makes no concessions to the Great Unwashed. OTOH valet's code-based "visual" views very clearly indicate open elements at any error, in (IMO) a clear and elegant way. A readymade solution. > Just as a reminder; the error parsing code is, as you know, very fragile. So > thread carefully when you modify it! <LeitMotif>XML Messages</LeitMotif> -- Nick Kew Nick's manifesto: http://www.htmlhelp.com/~nick/
Received on Friday, 16 April 2004 17:58:10 UTC