|DOCTYPE W3C is there any use ?|
no w3c validation, still page runs on netscape, opera, ie ?
| 9:44 pm on Jun 3, 2002 (gmt 0)|
I keep coming back to this forum, for the answers not found elsewhere ! :)
All my pages are made out of tables, they all show fine in opera and ie, 2/3 slight "errors" with netscape. But when i tried the validation "O MaN", i dont really feal like changing this now, since i want to spend my time on expansion, after optimizing it the last week, thanx to all your wunderfull knowhow ! :)
In Short; Why Should i Care about the w3c ?
| 9:49 pm on Jun 3, 2002 (gmt 0)|
There was a whole thread on tables, design, and W3C some time ago - you might get some useful info here:
Another thread on "Why Validate" here:
[edited by: Mardi_Gras at 9:56 pm (utc) on June 3, 2002]
| 10:00 pm on Jun 3, 2002 (gmt 0)|
Thanx Mardi_Grass :)
[edited by: HoMeR at 10:01 pm (utc) on June 3, 2002]
| 10:05 pm on Jun 3, 2002 (gmt 0)|
For sure! The extra work is worth the effort. You'll learn quite a bit just by fixing the errors the w3c finds as well. win/win situation homer.
| 10:10 pm on Jun 3, 2002 (gmt 0)|
I agree madcat. I learned a ton fixing my original HTML mess. It also spurred me on to begin CSS, and eventually XHTML.
[edited by: Axacta at 10:11 pm (utc) on June 3, 2002]
| 10:16 pm on Jun 3, 2002 (gmt 0)|
That's what has always amazed me! One of the very best tools for learning proper HTML coding has been available online at the W3C.org site for a long time.
It's an unforgiving teacher, but a fair one. And... it doesn't hold grudges! Once your code validates it awards you with a certificate! ;)
I wonder how many coding problems could be "figured out" if the coder simply made uses of a validation service? Not only does it tell you what is wrong... it also teaches the proper terminology.
Once you develop a taste for <!doctype> and validation, you will want to apply it to all of your pages.
| 10:23 pm on Jun 3, 2002 (gmt 0)|
As far as validating goes .. It's a pain to convert your old pages .. But, interestingly enough, those updated pages look ok in older browsers as well.
We are all so used to "hacking" the pages to look ok in every single browser. I recommend writing XHTML code from now on, using full CSS.
Not only will you save lots of code, but your pages will be easier for you to update. Also, the pages will look ok in newer browsers since they will already be compatible with those ;)
| 12:03 pm on Jun 5, 2002 (gmt 0)|
Thanx Again All, i'me going for the certificate ! win/win ;)