The quick brown fox jumped over the lazy dogs.
The quick brown fox jumped over the lazy dogs.
The quick brown fox jumped over the lazy dogs.
The quick brown fox jumped over the lazy dogs.
The quick brown fox jumped over the lazy dogs.
You have to view this in Firefox with the proper add-on to see this in action.
The MacBook Pro I ordered has just shipped direct from the factory in China.
I placed the order just before the current shipping delay received a bump to 7-10 days from 5-7 days. Demand must be pretty strong for the new LED-backlit, Santa Rosa machines.
I haven't bought many computers in the past several years, but three Macs within the last seven years might be considered many to some folks:
| Date of purchase | Computer | CPU |
|---|---|---|
| 2000-04-28 | PowerMac | 400 MHz PowerPC G4 |
| 2005-08-20 | Mac Mini | 1.25 GHz PowerPC G4 |
| 2007-07-03 | MacBook Pro | 2.2 GHz Intel Core 2 Duo "Santa Rosa" |
Anybody who views the XHTML source of this page will see that there's an XML declaration (XHTML is XML, after all) but no doctype declaration. A doctype declaration may have usefulness in HTML, but it is needless in XHTML. I am so glad Rusty Elliotte Harold proclaimed the gospel about validity in XHTML:
XML doesn’t have to be valid!
He even boldfaced this sentence in addition to putting an exclamation point at its end. (By the way, I also agree with his overall pronouncement against microformats.)
In the future, I'll likely mix the <canvas> tag with some SVG on this site. Try to find a DTD that will validate such an XHTML document. It's really well-formedness that's important when you're dealing with anything XML-based (namespaces have importance, too).
Break with convention, align yourself with modern markup practices, and go DTD-less.
I learned about XHTML a long time ago, but I'll admit that it hasn't been that long since I learned that XHTML should be served with a MIME type of application/xhtml+xml. I went ahead and converted a separate blog I run to use XHTML with the proper MIME type. And I converted that blog to Serendipity because of its superiority to MovableType, which the blog was using originally.
Serendipity has proven to be a pretty good platform for serving XHTML with the proper MIME type. The lead developer, Garvin Hicking, has been very responsive to fixing problems in the PHP-based software that generate non-well-formed XHTML.
So I'm using Serendipity for this blog also. Naturally, I'm using XHTML and application/xhtml+xml, and I refuse to use any kind of content negation here just because one browser hasn't been updated over the past half decade to recognize this MIME type.