Forum Moderators: open

Message Too Old, No Replies

various HTML standards and W3C validator

html 4.0, 4.01 strict, transitional, character encoding

         

pawel

4:40 pm on May 13, 2003 (gmt 0)

10+ Year Member



There are so many different standards of what a correct HTML document should look like, but, from what I see, few sites comply with them. W3C validator allows for testing pages against those standars, and it's quite rarely that pages are correct!
Say, Yahoo - doen't even start parsing the page, as no encoding information is available, then, after fixing that, TONS of errors show up!
Or this site - again, Validator says "no encoding labelling". What's wrong?
So, my questions are
(1)is there sth wrong with the Validator itself, or just almost all the pages in the web are not correct?
(2)are there any statistics showing the percentage if pages being correct HTML 4.0, 4.01 Strict, Transitional etc documents?

lorax

4:50 pm on May 13, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Re: validator - most folks don't even know there is such a thing as valid code let alone that there are different DOCTYPES and a validator to check for compliance.

Your second question is an interesting question. I'm not aware of any studies that would answer it though I'd be curious to see what the demographics are.

tedster

5:00 am on May 15, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



statistics showing the percentage if pages being correct HTML

Just a guess here, but taking the number of web pages at 3 billion, the number of VALID pages is going to be far, far less than 1% right now. 1% would be 30 million valid pages, and I doubt that it's anywhere near 1 million.

A lot of the reason is lack of awareness. Some of the reason is also practical, related to Content Management Systems and other parts of the development process. Many organizations simply need their content out there, fresh, early and often. If that can't be done easily, even transparently with the tools they have on hand, then they won't bother getting the code to validate, as long as it displays well in most browsers. For now validation can appear to be a unnecessary drain on resources.

The move to valid code is really the cutting edge. Ultimately it will allow the Internet medium to grow and mature, and it makes a heck of a lot more sense than for browser makers to build in what they should think is the proper amount of forgiveness.

In what other technical medium do we expect the "player" to forgive improper encoding? The Internet cannot mature beyond a certain limit while cowboy code is the rule. So we're at the very beginning of a change. How fast we each get with the change is a personal choice or a business choice. For now, the game is mainly about raising awareness that validation IS a choice.

There is also a carrot involved here, not just a stick. Do you want search engines to gobble up your content? Validate the code. Do you want to have solid instructions that will give good results on all kinds of devices? Validation is the answer.