By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,866 Members | 2,039 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,866 IT Pros & Developers. It's quick & easy.

Validation error: Line: 0 Context : body

P: n/a
The W3C CSS Validator was fine with http://wallysanford.com until this
afternoon. Now it gives this error message:

" Line: 0 Context : body
Parse Error - "

The page validates as XHTML. Any ideas will be appreciated. Thank you.

Jul 20 '05 #1
Share this Question
Share on Google+
13 Replies


P: n/a
On Mon, 01 Mar 2004 01:42:16 GMT, Wally Sanford
<Pl***********************************@wallysanfor d.com> wrote:
The W3C CSS Validator was fine with http://wallysanford.com until this
afternoon. Now it gives this error message:

" Line: 0 Context : body
Parse Error - "

The page validates as XHTML. Any ideas will be appreciated. Thank you.

The errors are in your print styles. At-rules must always be first in the
stylesheet. Move the at-rule to the top and correct the rampant errors
within, as explained in the report.
Jul 20 '05 #2

P: n/a
On Mon, 01 Mar 2004 00:02:49 -0500, Neal <ne*****@spamrcn.com> wrote:
The errors are in your print styles. At-rules must always be first in
the stylesheet. Move the at-rule to the top and correct the rampant
errors within, as explained in the report.


Sorry, the warning is referring to your a element for screen.
"font-family: Verdana;" should include a generic at the end. (You are
aware that Verdana is problematic?)
Jul 20 '05 #3

P: n/a
Neal wrote:
On Mon, 01 Mar 2004 00:02:49 -0500, Neal <ne*****@spamrcn.com> wrote:
The errors are in your print styles. At-rules must always be first in
the stylesheet. Move the at-rule to the top and correct the rampant
errors within, as explained in the report.

Sorry, the warning is referring to your a element for screen.
"font-family: Verdana;" should include a generic at the end. (You are
aware that Verdana is problematic?)


He may be; I'm not! I know that Verdana is a Windows font,
but will a declaration like this

font: 700 100% verdana, arial, sans-serif;

have other problems that I don't know about?

Cheers,

--
jc

Remove the -not from email
Jul 20 '05 #4

P: n/a
On Mon, 01 Mar 2004 07:59:45 +0000, Jeremy Collins
<jd********@ntlworld-not.com> wrote:
He may be; I'm not! I know that Verdana is a Windows font,
but will a declaration like this

font: 700 100% verdana, arial, sans-serif;

have other problems that I don't know about?

Cheers,

Compare Verdana to other fonts at the same size. Verdana appears bigger
for its size, so you generally will find second-choice fonts for Verdana
at your desired size look too small.

See http://www.xs4all.nl/~sbpoley/webmatters/verdana.html
Jul 20 '05 #5

P: n/a
Neal wrote:
Compare Verdana to other fonts at the same size. Verdana appears bigger
for its size, so you generally will find second-choice fonts for Verdana
at your desired size look too small.

See http://www.xs4all.nl/~sbpoley/webmatters/verdana.html


Yup, that makes sense. I think I'll follow this advice.

--
jc

Remove the -not from email
Jul 20 '05 #6

P: n/a
In article <Yx*******************@newsread1.news.atl.earthlin k.net>,
"Wally Sanford" <Pl***********************************@wallysanfor d.com> writes:
The W3C CSS Validator was fine with http://wallysanford.com until this
That URL is a redirect. You're better off using a real URL.
" Line: 0 Context : body
Parse Error - "
Sounds like failure to fetch something. Perhaps one of your servers
was unreachable (using two of them doubles the risk of that kind of thing).
The page validates as XHTML. Any ideas will be appreciated. Thank you.


Legacy XHTML - you should upgrade (it's not 1997 any more). And it relies
on more than one dodgy Appendix C trick to work: apart from the content-type,
you have leading whitespace (which XML does not permit).

--
Nick Kew
Jul 20 '05 #7

P: n/a
ni**@hugin.webthing.com (Nick Kew) wrote:
... And it relies
on more than one dodgy Appendix C trick to work: apart from the content-type,
you have leading whitespace (which XML does not permit).


Please elaborate. What is this leading whitespace that XML does not permit?
Are you referring to the single line feed before the line beginning "<!DOCTYPE"?

--
Karl Smith.
Jul 20 '05 #8

P: n/a

"Nick Kew" <ni**@hugin.webthing.com> wrote in message
news:1m************@webthing.com...
That URL is a redirect. You're better off using a real URL.
Thanks, Nick. The redirect is sometimes problematic. A direct link is
http://home.earthlink.net/~wallysanford/.
" Line: 0 Context : body
Parse Error - "


Sounds like failure to fetch something. Perhaps one of your servers
was unreachable (using two of them doubles the risk of that kind of

thing).

I've removed the whitespace (and corrected some the errors pointed ouy in
subsequent messages, and still get the same parse error from
http://home.earthlink.net/~wallysanford/ as well as www.wallysanford.com.
Those two pages are on different servers: one at my house and one at my ISP,
so I'd guess the problem is elsewhere.
The page validates as XHTML. Any ideas will be appreciated. Thank you.


Legacy XHTML - you should upgrade (it's not 1997 any more). And it relies
on more than one dodgy Appendix C trick to work: apart from the

content-type, you have leading whitespace (which XML does not permit).
What did you have in mind for me to upgrade?
--
Nick Kew

Jul 20 '05 #9

P: n/a
"Neal" <ne*****@spamrcn.com> wrote in message
news:op**************@news.rcn.com...
On Mon, 01 Mar 2004 01:42:16 GMT, Wally Sanford
<Pl***********************************@wallysanfor d.com> wrote:
The W3C CSS Validator was fine with http://wallysanford.com until this
afternoon. Now it gives this error message:

" Line: 0 Context : body
Parse Error - "

The page validates as XHTML. Any ideas will be appreciated. Thank you.


The errors are in your print styles. At-rules must always be first in the
stylesheet. Move the at-rule to the top and correct the rampant errors
within, as explained in the report.


I moved the print rules to the top of the style sheet and corrected the
rampant errors. Still, both at http://wallysanford.com/ and
http://home.earthlink.net/~wallysanford/ the Parse Error remains.

Any other ideas?
Jul 20 '05 #10

P: n/a

"Neal" <ne*****@spamrcn.com> wrote in message
news:op**************@news.rcn.com...
On Mon, 01 Mar 2004 00:02:49 -0500, Neal <ne*****@spamrcn.com> wrote:
The errors are in your print styles. At-rules must always be first in
the stylesheet. Move the at-rule to the top and correct the rampant
errors within, as explained in the report.


Sorry, the warning is referring to your a element for screen.
"font-family: Verdana;" should include a generic at the end. (You are
aware that Verdana is problematic?)


I was aware that it displayed larger. I've removed it, made the fonts Arial,
Helvetica, sans-serif; and the parse error remains.
Jul 20 '05 #11

P: n/a
"Wally Sanford"
<Pl***********************************@wallysanfor d.com> wrote:
A direct link is http://home.earthlink.net/~wallysanford/.
> " Line: 0 Context : body
> Parse Error - "


The code contains:

body, {
font-family: Arial, Helvetica, sans-serif;
font-size: 10pt;
}

Get rid of the comma.

Steve

--
"My theories appal you, my heresies outrage you,
I never answer letters and you don't like my tie." - The Doctor

Steve Pugh <st***@pugh.net> <http://steve.pugh.net/>
Jul 20 '05 #12

P: n/a

"Steve Pugh" <st***@pugh.net> wrote in message
news:4s********************************@4ax.com...
"Wally Sanford"
<Pl***********************************@wallysanfor d.com> wrote:

Get rid of the comma.

Steve

--
"My theories appal you, my heresies outrage you,
I never answer letters and you don't like my tie." - The Doctor

Steve Pugh <st***@pugh.net> <http://steve.pugh.net/>


Duh on my part. Thanks much, Steve. It validates now.
Jul 20 '05 #13

P: n/a
On Wed, 03 Mar 2004 09:13:37 GMT, Wally Sanford
<Pl***********************************@wallysanfor d.com> wrote:
I moved the print rules to the top of the style sheet and corrected the
rampant errors. Still, both at http://wallysanford.com/ and
http://home.earthlink.net/~wallysanford/ the Parse Error remains.

http://jigsaw.w3.org/css-validator/v...usermedium=all
says it's OK.
Jul 20 '05 #14

This discussion thread is closed

Replies have been disabled for this discussion.