Let’s Try This Standards Stuff
Right then, standards here we come. I’ve got my half-price copy of Zeldman’s book [http://www.amazon.co.uk/gp/redirect.html?ie=UTF8&location=http%3A%2F%2Fwww.amazon.co.uk%2Fexec%2Fobidos%2FASIN%2F0735712018%2F&tag=hmobiuscom-21&linkCode=ur2&camp=1634&creative=6738] and I’m not afraid to use it. First crack - write some core pages in XHTML 1.1 [http://www.w3.org/TR/xhtml11/]? Why 1.1 and not 1.0 [http://www.w3.org/TR/xhtml1/]? Because it’s there mostly. I’d use XHTML 2.0 [http://www.w3.org/TR/xhtml2/] except that it will keep changing and if I’m that desperate I could always transform it with a style sheet anyway later on. And I know it won’t be completely valid XHTML 1.1 because the right MIME-Type isn’t served up to browsers that give a damn, but at least the xml is a start, yes? Supplemental pages will appear later.
First stop - validation. The W3C provides a validation service [http://validator.w3.org/] for (X)HTML, CSS and WAI standards. Just plug in the address of the page you want validated and sit back in horror as you are told how many things are actually wrong with it. Mixed case tags, quotes and equal signs looks like being the killers. Oops. Looks like VS Whidbey has some ace validation options too. Favelets.com [http://www.favelets.com] tries to provide an easier way of getting your page to the validator as well. Pretty nice, but watch for the Mac-only ones.
First few tweaks added to. Replaced usual apostrophe character ’ with this one ’ which is apparently the typographically correct apostrophe. Doesn’t matter for browsing but will do when pages are printed.Posted on October 9, 2003