Pages tagged doctype:

Coding like it's 1999 ~ Authentic Boredom

Recently I made the switch back to HTML 4 for DOCTYPEs and px for font-size (sound like 1999 again?), and I’ve tweeted about it occasionally. I’m documenting the switch more thoroughly here.
"I’ve chosen to go with HTML 4.01 Strict as the DOCTYPE in my projects moving forward, favoring it above XHTML 1.0 Strict and HTML 5. I’ll briefly explain my reasoning."
HTML 5 – In a nutshell, HTML 5 is the next major version of the hypertext markup language. The good news is meaningless div and span elements will be replaced by more meaningful elements such as nav, header, and video.
Cameron Moll on HTML5 and px for font-size
The Skinny on Doctypes
Proposes we use the skinny doctype? that's a doctype?
<!doctype html>, that's it.
At Google, we have this obsession with byte size. And by byte size, any “lack-therof” the better. Therefore the doctype you will find on most Google webpages while still triggering the browser into “standards mode” is as simple as you see below:
ケータイ3キャリアに対応するためのDOCTYPE宣言について |
XHTMLを使ってケータイサイトを作成する際には、HTMLの冒頭にDOCTYPE宣言を記述する必要があります。 先日からこの「DOCTYPE宣言」に関するブログエントリーが人気を集めているようなので、当サイトも触れてみようと思います。 下記2つのサイトでは、どちらもif文でユーザエージェントを判定して、DOCTYPEを出し分けるという処理を紹介しています。
django-html - Google Code
Want html form tags using a django form? This is what you need
Allows setting doctype and avoiding self-closing tags in forms, for HTML4. I'm finding Django's insistence on XHTML-style self-closing form tags quite annoying.
django html
This package represents an experimental approach to improving the way Django outputs form widgets. At the moment, widgets created using django.forms are outputted as XHTML (with self closing /> tags) even if the rest of your site uses HTML. This package solves this problem by introducing two new template tags: {% doctype %} and {% field %}.
<p>Some nice template tags for getting django forms to output valid html instead of the default xhtml. Nice for sites where you're working with html 4.</p>