|
spitfire -> RE: please review spam4it.com (1/22/2006 6:28:37)
|
As womble says, legacy sites will inevitably show validation errors. They were built before validation became the acceptable way of testing for good code practices, that provide solid, easily maintainable pages. Large sites cannot just be tweaked to validate and depending on how mal-formed the code is, it could mean a complete re-write - a bit like trying to turn a tanker around in mid-stream. But keep an eye on them, gradually they will fall due for re-writes and even some forum software can be modified to make it valid and quite accessible to all visitors.
dpf pointed you towards the problem - syntax. There is a mix of XHTML and HTML syntax in the code. Dreamweaver does not get things like variable closing ">" and "/>" wrong, nor does it mix capitalised tags <A HREF> with lower case ones within the same doctype. It is most probably not the code Dreamweaver actually gave you - how can it be expected to cope with some code (pasted?) from XHTML documents and some code from HTML. The problem is trusting in Dreamweaver always to get it right, no matter what stuff appears that is not Dreamweaver generated or Dreamweaver compatible.
A little test for you. Let's assume the home page started in Dreamweaver with a different doctype, say HTML 4.01 transitional. Apply that to your code instead of the XHTML 1.0 transitional it now carries. Validate - 7 errors only, instead of the 77 errors currently. Don't have nightmares now [sm=whistling.gif]
|
|
|
|
