Overhauling fruttenboel

It was time for a change. For the US but also for my websites. My table based websites were getting outdated and I wanted to do one big overhaul to a modern day web control language.
At first I wanted to migrate to HTML 4.01. But that is an old standard too. So why change one old standard for another old standard? Does'nt make sense. So I opted for 'XHTML 1.0'. It looked to be the best of both worlds. XHTML was promised to be modular and logical. Two features I could not find back in it, though.
I converted two full sections to XHTML. And I definitely need to keep the frames. All the typical frame associated disadvantages melt away like snow in the sun, if you use a googleBuster like my FrameStomper. I managed to produce webpages in XHTML and with some CSS that worked like a charm and produced neat webpages, that were even fine to print. Then I ran a few pages through the W3C validator. ZILLIONS of errors and warnings! The validator even issues error warnings on data area's! In an anchor statement there was a reference to an 'id' and the validator choked on it!
Converting HTML 3.2 to XHTML is a nightmare. You have to go through every single line. All linebreaks need to be changed due to the extreme XHTML syntax. XHTML is not structured. It is OVERstructured. Too much syntax. Too much structure. It may be a fine HTML variant for C++ coders but when you need to change the statement

   noresize = "yes"
   noresize = "noresize"
it's clear that you're showing signs of dementia. Or are a seasoned C++ coder. Or both. But that's another story. Please take a look in the 'Languages' section via the navigator.

Which version of HTML to use

HTML 3.2 is too old. And so is HTML 4.x. XHTML is overly complicated and only suited for C++ coders (not programmers; those work with Wirthian languages). But what else?
If you visit the site of our beloved sherriff's department (the w3c) you are overwhelmed by all versions of markup languages. All of them more exotic than the others. It's dazzling. The W3C is to the web, what the European Commission is to Europe: too much rules for a too small subject. Instead of creating a lean system and ditto standards, they keep on creating new dynosaurs and they're even proud of it!
But, lucky for us, the solution to this all is on the W3C pages: they need money and they have a beggers paragraph on top of many pages. So, if you care for the web and want accessible HTML standards, DON'T spend a cent on the W3C beggars action. Put them on a diet. The web needs it.
Still, I didn't know how to commence. The trials with XHTML were not too comforting. XHTML has no real logic in it at all. Only syntax laws! To make life harder for human HTML creators.

The rescue came from a friend in Spain who tipped me about modern browsers and their very fast internal javascript engines. And their interactions with the new properties of HTML 5. So I started a hunt for HTML 5. Of course, the W3C has a document on HTML 5. It's only 900 pages of text. Although the lot of them live quite close to ETHZ, none of them ever understood anything of the works of Niklaus Wirth. Why not present the HTML in EBNF and some simple examples? Why always treat the HTML composers as if they were morons? It's ridiculous to see how even the simplest of keywords is explained.
If that was not bad enough, the text also cannot be printed due to hovering windows that repeat on every page. But somehow, that was what I expected from those creeps.
In the end I found this: http://dev.w3.org/html5/html-author/ and now that I see it, I find out this is W3C as well. Hmm. perhaps one of those guys still has some senses and created this document. It's a mere 16 pages (2 pages per sheet, doublesided printing) of text. Acceptable.
Then I found this site: http://www.webmonkey.com/2010/02/building_web_pages_with_html_5/ which looks much better. Written by users and with examples.

The move towards HTML 5

My pages will be converted to HTML 5. This page is written with HTML 5. If your browser has difficulties showing the contents (I wonder if you could still read this letters then) switch over to Seamonkey or another Mozilla based browser. It's time for a change. Not only for Obama. Also for Bill (or Steve or whatever his current name is). And, for the record:

This webpage is fully written in HTML 5!

The webbroser I use as standard on all machines (even the dreaded Windows) is SeaMonkey version 1.1.16 or above. So if IE won't run HTML 5 pages, do yourself a favor and download the free SeeApe.

Some interesting links

Some source

I couldn't resist putting some simple HTML 5 source online. Here is the default file that I use for starting out with, for the (newly formed) HTML 5 section:
<!doctype html>
<html lang="en">

    if (parent.location.href == self.location.href)
     { window.location.href =
   // -->
  <meta charset = utf-8>
  <meta name="Author" content="jan verhoeven">
  <meta name="GENERATOR" content="jan and jed">
  <meta name="Description" content="HTML 5 : ">
  <title>HTML 5 : </title>
  <link type="text/css" rel="stylesheet" href="../frutt.css">
  <p class = "header"> </p>
  <p class = "summ">
   Page created on <datum> and
    document.write ("last revised on " + document.lastModified + "<br>");
    document.write ("This page located at " + document.URL + "<br>");
  <p class = "GB">Page equipped with googleBuster technology!</p>
The most important differences so far:

Page created on 8 August 2009 and