W3C home > Mailing lists > Public > www-validator@w3.org > August 2002

Re: XHTML Validation service - a comment

From: Ron Aitchison <ron@zytrax.com>
Date: Sat, 24 Aug 2002 21:09:33 -0400 (EDT)
Message-ID: <3D683066.D24D35F2@zytrax.com>
To: Martin Duerst <duerst@w3.org>
Cc: Nick Kew <nick@webthing.com>, www-validator@w3.org




Will try all current conversion files on validator.w3c.org:8001 - don't know if
Nick has done the update but will keep all failing files until I hear status from
Nick.
Regards

Martin Duerst wrote:

> I have just committed a first, sketchy solution for this,
> please see http://dev.w3.org/cvsweb/validator/httpd/cgi-bin/check
> (revision 1.208). Needs some checking and testing
> (which I can't do with my present setup).
> I hope Nick can check this out to :8001, and you can give
> it a try.
>
> Regards,    Martin.
>
> At 22:50 02/07/14 -0400, Ron Aitchison wrote:
>
> >Nick:
> >Thanks for the response. Figured there had to some reason to inhibit or abort.
> >
> >I would still suggest that on-balance (whatever that means) the good may
> >outweigh the dangers of incorrect formatting. I would make two further
> >comments here in terms of invalid chars affecting line numbering.
> >a. the validator has calculated some line number (which may be incorrect due
> >the invalid formatting) Best let the page author see what the validator
> >figured. Everyone is then on the same (maybe incorrect) hymn sheet.
> >b. I would certainly suppress the line number cross reference because it could
> >become very dangerous.
> >Regards
> >
> >Nick Kew wrote:
> >
> > > On Sun, 14 Jul 2002, Ron Aitchison wrote:
> > >
> > > > This leads to my comment, I have just hit some pages in which the XHTML
> > > > validator is complaining that certain line numbers do not contain valid
> > > > UTF-8 codings. However in spite of checking the 'Show Source' option the
> > > > validator aborts after this check and does not display the source.
> > >
> > > Yes, that sounds about right.  If the validator shows source in the
> > > presence of invalid characters, it risks being wildly wrong: what if
> > > such a character affects line numbers?  OTOH, a simple listing might
> > > indeed be helpful more often than not.
> > >
> > > In terms of the validator innards, there is some complexity involved.
> > > Validator shoves the input through iconv before applying OpenSP to
> > > do the actual validation.  If there is a charset problem, there is
> > > no satisfactory answer to the question of which input (before or
> > > after iconv) to show.  The approach adopted by the WDG validator
> > > might work better in this instance, though I can't say without
> > > a URL to look at.  The XML Validation service at Site Valet won't
> > > fix this particular problem, but might help you in any case.
> > >
> > > --
> > > Nick Kew
> > >
> > > Available for contract work - Programming, Unix, Networking, Markup, etc.
> >
> >--
> >Ron Aitchison               http://www.zytrax.com
> >ZyTrax                      mailto:raitchison@zytrax.com
> >                             70 rue Notre Dame West
> >                             Montreal Quebec H2Y 1S6
> >                             Tel:(514) 285.9088
> >

--
Ron Aitchison               http://www.zytrax.com
ZyTrax                      mailto:raitchison@zytrax.com
                            70 rue Notre Dame West
                            Montreal Quebec H2Y 1S6
                            Tel:(514) 285.9088
Received on Saturday, 24 August 2002 21:36:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:03 GMT