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

RE: problem with validator

From: Lee A. Jones <lee@archid.co.uk>
Date: Fri, 9 Aug 2002 08:03:47 -0400 (EDT)
To: "Terje Bless" <link@pobox.com>, "W3C Validator" <www-validator@w3.org>
Cc: "Thanasis Kinias" <tkinias@optimalco.com>

My second question to you, is that in your considered opinion - do you think
it is DirectNIC's fault for inserting the null character?

I use Macromedia Homesite 5 to write my webpages, and if I upload the page
in question to any server not owned by DirectNIC then I validate correctly
with no problems. But if I validate from a page held on DirectNIC then it
inserts this Null character.

A techie guy at DirectNIC actually pointed out to me that the validator
might be at fault - do you think the validator inserts a null character? OR
do you think DirectNIC inserts a null character?

A little insight into this, is that I pay for DirectNIC to host my domain
without banner ads. A banner ad is usually inserted into the bottom of the
<head> container of every page I upload, by a server daemon. Look at the
code on the page http://www.aeropork.com/ and you'll notice that when you
view source and highlight any text past the </html> tag, there are a few
characters of blank space...

I know for a fact that those characters are not there when I upload the
file. The page incidentally does not validate because of these null

I am unsure whether to complain to DirectNIC without first getting
confirmation from you guys - even giving the support guy at DirectNIC your
address so you can reply should he approach you.

Let me know what you think



-----Original Message-----
From: Terje Bless [mailto:link@pobox.com]
Sent: 08 August 2002 21:03
To: W3C Validator
Cc: Lee A. Jones; Thanasis Kinias
Subject: Re: problem with validator

Thanasis Kinias <tkinias@optimalco.com> wrote:

>Rechecking, it's just the DOCTYPE override that influences it.  Setting
>an ISO-8859-1 charset override (for me) makes no difference.

Further hand-holding from Gisle Aas (this guy is *fast*! ;D) shows up a bug
in my code. Turns out we forgot to flush the filehandle when feeding
HTML::Parser leading to truncated files whenever the DOCTYPE override was
in effect. Nasty! But fixed now. Many many thanks to you both for bringing
this to light!

The moral of the story: Always call $p->eof()! :-)

When I decide that the situation is unacceptable for me, I'll simply fork
the tree.   I do _not_ appreciate being enlisted into anyone's holy wars,
so unless you _really_ want to go _way_ up in my  personal shitlist don't
play politics in my vicinity.                   -- Alexander Viro on lkml
Received on Friday, 9 August 2002 16:48:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:17:34 UTC