MY Site looks like Poop !!! - Page 8

**spartas** · September 23rd, 2004, 11:15 PM

Your doctype is telling the validator you have a HTML page, not an XHTML page. Change the doctype definition to the one below and it will recognize your page and validate it to XHTML standards instead of HTML standards.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

**bcinelli** · September 24th, 2004, 2:50 AM

Haugland .. weren't we shooting for XHTML ? instead of HTML? ... is it possible we can still shoot for XHTML .. i mean where only a few away from being XHTML validated .

theward · September 24th, 2004, 10:28 AM

Quote:

Originally Posted by bcinelli

Haugland .. weren't we shooting for XHTML ? instead of HTML? ... is it possible we can still shoot for XHTML .. i mean where only a few away from being XHTML validated .

http://validator.w3.org/check?uri=ht...onal&verbose=1

the iFrame is causing alot of problems. iFrames = bad technology. I still don't use them to this day.

all singular tags need a /> closer... this includes your meta tags, ALL your input tags, etc. Missing a closer generates 2-3 errors each. (element not allowed here, missed closing here, start was here) :: make sure you READ the small black text to find out what the error means. don't just look at the names!

"</IFRAME>" all elements need to be in lowercase.

and also make sure you have the right DOCTYPE listed at the top of the document. I'm only force-validating as XHTML 1.0 Trans here.

**bcinelli** · September 24th, 2004, 10:30 AM

Quote:

Originally Posted by theward

http://validator.w3.org/check?uri=ht...onal&verbose=1

the iFrame is causing alot of problems. iFrames = bad technology. I still don't use them to this day.

all singular tags need a /> closer... this includes your meta tags, ALL your input tags, etc. Missing a closer generates 2-3 errors each. (element not allowed here, missed closing here, start was here) :: make sure you READ the small black text to find out what the error means. don't just look at the names!

"</IFRAME>" all elements need to be in lowercase.

and also make sure you have the right DOCTYPE listed at the top of the document. I'm only force-validating as XHTML 1.0 Trans here.

I want it to be XHTML 1.0 Trasitional .. HTML 4.0 was just too easy .. do you have the DOCTYPE tags for XHTML 1.0 trans?

im gonna go ahead and close the crap that is screwin it up. .. then upload.

theward · September 24th, 2004, 10:32 AM

Quote:

Originally Posted by bcinelli

I want it to be XHTML 1.0 Trasitional .. HTML 4.0 was just too easy .. do you have the DOCTYPE tags for XHTML 1.0 trans?

im gonna go ahead and close the crap that is screwin it up. .. then upload.

MY Site looks like Poop !!!

**bcinelli** · September 24th, 2004, 10:46 AM

I put all of that in .. what abou tthe

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

H · September 24th, 2004, 1:11 PM

I'm in the lab for another 30 minutes, but I get home in another 2 hours or so. I'll lend a hand when I can.

I agree with <iframes> being bad, but sometimes you gotta use it.

theward · September 24th, 2004, 1:17 PM

Quote:

Originally Posted by Haugland

I agree with <iframes> being bad, but sometimes you gotta use it.

Such as? Name a situation and I'll name why usage of an iframe is bad plus an alternative. I never, ever recommend iframes to clients. iframe is about as revolutionary as font tags.

H · September 24th, 2004, 1:33 PM

Quote:

Originally Posted by theward

Such as? Name a situation and I'll name why usage of an iframe is bad plus an alternative. I never, ever recommend iframes to clients. iframe is about as revolutionary as font tags.

Honestly -- Can't think of one. Give me credit.. I woke up late and it's 9:30am

September 23rd, 2004, 11:15 PM	#64 (permalink)
spartas surmunity freak Comfy Contributor Joined in Sep 2004 Lives in Baton Rouge, LA, North Amewica, USA, Earth Hosted on D68; Serva; Pass15 143 posts Gave thanks: 0 Thanked 0 times	Your doctype is telling the validator you have a HTML page, not an XHTML page. Change the doctype definition to the one below and it will recognize your page and validate it to XHTML standards instead of HTML standards. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> __________________ Server: Pass15 twwright.net NoE Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Firefox/1.0 (Ubuntu package 1.0.2) I run ubuntu hoary!

September 24th, 2004, 2:50 AM	#65 (permalink)
bcinelli B - UNIT!! Super #1 Joined in Aug 2004 Lives in Long Island, NY Hosted on Pass23 1,408 posts Gave thanks: 0 Thanked 0 times	Haugland .. weren't we shooting for XHTML ? instead of HTML? ... is it possible we can still shoot for XHTML .. i mean where only a few away from being XHTML validated . __________________ All sites hosted on Pass23 -- Dirty Dalerz Inc. --Dirty Dalerz (dot) com--ZooYorkFreak (dot) com--NyLiBeerpong(dot) com--Ugh.. Myspace

September 24th, 2004, 10:46 AM	#69 (permalink)
bcinelli B - UNIT!! Super #1 Joined in Aug 2004 Lives in Long Island, NY Hosted on Pass23 1,408 posts Gave thanks: 0 Thanked 0 times	I put all of that in .. what abou tthe <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> __________________ All sites hosted on Pass23 -- Dirty Dalerz Inc. --Dirty Dalerz (dot) com--ZooYorkFreak (dot) com--NyLiBeerpong(dot) com--Ugh.. Myspace

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Rate This Thread
Rate This Thread:

September 24th, 2004, 1:11 PM	#70 (permalink)
H after g, before i Resident. Joined in Jul 2004 Lives in N,BC,CA 8,089 posts Gave thanks: 48 Thanked 131 times	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> Of course we can go to XHTML I'm in the lab for another 30 minutes, but I get home in another 2 hours or so. I'll lend a hand when I can. I agree with <iframes> being bad, but sometimes you gotta use it.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)