w3c compliance? site looks funny 1

[zavsays]

I've got a long-established site that I started building while trying to learn css. I've recently installed OSX for Mac and dowloaded the latest browsers (Camino, Safari) and I'm seeing problems with the site I didn't know where there (blank where type should be, formatting changed). This must be a W3C compliance issue.

My site is quite large and I know there's likely a cacophony of coding problems on it. I started to rebuild (clear out the code and re-insert it onto the text) but the outcome was weird. The text came out better but the Template was shifting around from page to page (banner ended up in different places, index spread out on some pages). I've got a little knowledge of coding...that is to say...I could paste code from what looks good to what looks bad but in my case, that didn't always make things better.

Has anyone else gone through this sort of thing. Is there any features in Dreamweaver MX that help with W3C that are not in Dreamweaver 4? "Clean up HTML" command does't do the trick. I'm not looking forward to rebuilding this monster.

Any suggestions other than "read the WC3 site" would be appreciated.

Thanks.
Zavsays

http://www.bigbandsandbignames.com/

 

[lebisol]

hmmmm this a tought one....you say that this is a "monster" site...
the only way is really doing it manually so ur in some pain but you can test your pages before doing anything:

http://validator.w3.org/

...unfortunately at this point u really need to know HTML codeing behind the DW interface
Good Luck!

 

[boyfromoz]

file> check page> validate markup

I ahd a similar problem, recently bought a mac to test sites on, and fund mac browsersmuch elss forgiving. Pages that would render properly in IE6 woudl be all over the show ona amc.

Problem normally is in table structyre. You've moved something somewhere, and deleted a start or clsoing tag of a table cell/row without relaising. IE6 will clsoe them anyway, mac browsers oftern won't and then get confused as to where to put things.

Yes, you need to be able to read code to fix this OR start again.