tw3k: url sever each format to a url the (x)html(s), the feeds, json etc. subAuth
tw3k: url sever each format to a url
the (x)html(s), the feeds, json etc.
subAuth (via Twitter / tw3k)
tw3k: url sever each format to a url
the (x)html(s), the feeds, json etc.
subAuth (via Twitter / tw3k)
After looking at the current landscape of doctypes I’m not ready to jump on the html5 bandwagon. Html5 Looks promising and I’ll take it when it is ready. With a proper presentation layer in place it will be a trivial change to make. And, as much as I’d like to serve up some xhtml 1.1 with application/xhtml+xml IE, of course, isn’t there. My only real problem at this point is dealing with all the html bloggers paste into their posts. Thank goodness for tidy. :) But…. a few things still slip through. So rather than handing out a style guide, regex’n teh toobz or using javascript, which would end up being regex fuckery anyways, I’ve decided the best w3c validation hack lies within the DTD. Not only is there ample information out there for extending xhtml but it’s a lot less work than any of the other methods of validating flash I’ve seen. Many of those methods work well enough if your adding a little html yourself but not when your consuming feeds. Thus, I present to you “DTD XHTML 1.1 plus tw3k 1.0.” A w3c flash validation hack. <!DOCTYPE html PUBLIC “-//groups.firedoglake.com//DTD XHTML 1.1 plus tw3k 1.0//EN” “http://groups.firedoglake.com/DTD/xhtml11-tw3k.dtd” > If you use it and/or want to play feel free. Here are the files and a small test page.
In a nutshell the xhtml11.dtd is the standard dtd with the object module removed. xhtml11-tw3k.dtd defines the embed element and defines the object element just as the w3c does, they wrote it, but with the addition of allowing embed to be nested within the object element. I also added the target and border attributes because tidy just wouldn’t git’em.