novatech @ pengganas

Site valid xhtml, valid css valid rss with clean and clear code required a serious effort. Talking about writing clean codes, there will be too many rules to be followed. Normally there are common errors like leaving closing tag. Some errors will make themselves obvious when viewing the page in a browser, as when a missed closing “</b>” tag.

Then a missed “</table>” tag not affecting your site if you view it with IE, because IE is forgiving browser, but not other browsers like firefox/safari/opera.
The use of special characters such as ampersands (&) and (©) instead of the more valid and appropriate entity tags “&” and “©” while they may appear as you intended in some browsers, may appear as other symbols entirely, depending on how the browser chooses to read the symbol.

Talking about this craps, actually i’m finished doing 80% re-validation on my css, rss and xhtml codes. And for the css rule i got this warning

“You have no background-color with your color”

wtf, to avoid this warning i have to put color and background-color in all my css, and that gonna take a lot of modification of my css file and that will increases file size. wtf

just ignore that damn warning like it never happened ..lol

More…

Actually who cares about valid/invalid in xhtml and css, as long as it work and can be view. If you view it from normal perspective then it’s fine, but from professionalism perspective it’s something not good. :)

Reference

The internet says:
Why is valid code important?
1.There are many advantages to writing valid code. The most immediate benefit is cross-browser compatibility. While there are differences in the way that valid code renders between browsers (ever noticed the difference between the appearance of a horizontal rule in Netscape and in Internet Explorer?), valid HTML ensures that your page will work across the board. The W3C calls this “interoperability.”
2.Valid code also prepares your pages for new coding languages. As new versions of HTML and new mark-up languages are developed, so are various applications to translate one set of tags to another. If your HTML is valid, chances that the transition of your code to the new standards will be smoother and cause fewer headaches for you and for anyone else involved.

From W3C Markup Validation Service
Why should I validate my HTML pages?
One of the important maxims of computer programming is: Be conservative in what you produce; be liberal in what you accept.
Browsers follow the second half of this maxim by accepting Web pages and trying to display them even if they’re not legal HTML. Usually this means that the browser will try to make educated guesses about what you probably meant. The problem is that different browsers (or even different versions of the same browser) will make different guesses about the same illegal construct; worse, if your HTML is really pathological, the browser could get hopelessly confused and produce a mangled mess, or even crash.
That’s why you want to follow the first half of the maxim by making sure your pages are legal HTML. The best way to do that is by running your documents through one or more HTML validations.

sorry for my bad english