In my last content about creating an (X)HTML page, I spend some time dealing with the DOCTYPE tag that every documents need in the first place. I did give you several examples, but as one reader input it, I really glossed with the idea and I really should have spent some more time examining the several types of DOCTYPE values and whatever they mean. So as opposed to jumping right into METATAGS, I'm going to spend a little added time dealing with the DOCTYPE marking.
The World Wide Word wide web Consortium (W3C), in ones own documentation, does define many different types of HTML - XHTML. In fact during the time I wrote this, there was 21 different DOCTYPE declarations listed around the W3C's Valid DTD directory page. And I'm quite sure that one could probable find as a good many more if you looked complicated enough, but the one's listed in the W3C's web page are the most frequent ones currently in utilize. Now just to renew your memory, a Document Type Quality (DOCTYPE) establishes what parts and attributes your document will use and what rules you intend to follow in generating your page. By using the ideal DOCTYPE you will ensure that your document will be rendered correctly utilizing a standards compliant web web browsers.
But what if you won't include a DOCTYPE statement in your own document or your DOCTYPE assertion is incomplete or improper? Well those same standards compliant browsers will drop into "Quirks" mode and assume your HTML or XHTML along with CSS is non-compliant. Suffice it to state, you won't get everything you thought you should get whilst your page may not sometimes be readable. This is obviously not what you would like to happen, so employing a DOCTYPE statement, and the proper DOCTYPE statement is vital. Now before we progress, a word about standards compliant browsers. Just because a browser claims for being standards compliant doesn't mean it can be. There are different models of standards compliant, so some browsers tend to be compliant than others. With any luck ,, some day all browsers will behave the identical, but for the time being that isn't true and it is often necessary to include code tailored for one browser so that browser will work as the other's do. These little differences have become know as hacks and for some programmers are just discomforts were a pill will not likely reach.
Ok, you point out, what DOCTYPE should I take advantage of. Well as I have always been writing this, a unique standard is emerging: HTML5. May i get a few oooo's and additionally ah's. Now depending on who you speak to, HTML5 is either a very important thing to happen to the world wide web or the worst. And also unfortunately, at this point in time, it's is not entirely support by any technique. Some are getting close up, but there is a strategies to go. So it's not something so you can get overly excited about, but since HTML5 comes with some compatibility with HTML4 together with XHTML 1, it does signify we can use the particular HTML5 DOCTYPE statement, yet basically code in HTML4 as well as XHTML 1. All this implies, by the way, will be that as more HTML5 issues become available, you won't must mess around with shifting your DOCTYPE statement. Alright, ok, you say, I obtain it, so what does the DOCTYPE statement appear to be? Ok, are you set? Here it is:
[!DOCTYPE html]
Which is it. It's that uncomplicated! [ replaces the for the purposes of not screwing up some article directories). The whole idea is to stop making things so complicated. So if you take the versioning out of the DOCTYPE statement, then it should be easier to be backward compatible. We will have to wait on that, but in the meantime, this sure save a lot of typing. No for those of you that are not convinced, here is the DOCTYPE I normally used until I switched to the HTML5 DOCTYPE:
[!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"]
This is the DOCTYPE for XHTML 1.0 - Transitional, and for the most part was the DOCTYPE of choice for most web pages. It was either this one or the HTML 4.01 - Transitional DOCTYPE, shown below:
[!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"]
Now it's interesting to note that the DOCTYPE for HTML5 is listed on the W3C's Valid DTD List page, but it is also noted that it is NOT a standard yet. Ok, but should you start using the HTML5 DOCTYPE now? The short answer is yes, but it really depends on your site. But here's something you might want to consider, Google uses the HTML5 DOCTYPE on their main search page. So even if you don't take advantage of all the new features currently available for HTML5, at least you'll be ready when it takes hold.
In my next article, I will begin to discuss METATAGS and how they should be used in your document's creation, so until next time .....
Home 
Thu Sep 15, 2011 4:50 pm