• WebM/VP8
• OGG/Theora
• MP4/h264

Build ffmpeg (version >= 0.6)

Create a directory, let's say "myvideos". All the comming commands will make sure that everything stays in this directory. Your system won't be altered.

Downloads:

• ffmpeg source code: here.

dependencies:

• vorbis: here (the version of you distribution should be ok: libvorbis-dev);
• x264: here;
• faac: here;
• theora: here.
• vpx:
  

  git clone git://review.webmproject.org/libvpx.git

Build:

mkdir ~/myvideos/dist

• un-compress;
• go to the source directory;
• ./configure --prefix=~/myvideos/dist && make && make install

Let's build ffmpeg:

$ LDFLAGS=-L$~/myvideos/dist/lib CFLAGS=-I~/myvideos/dist/include ./configure --prefix=~/myvideos/dist --enable-gpl--enable-nonfree --enable-libvpx --enable-libvorbis--enable-pthreads --enable-libx264 --enable-libfaac--enable-libtheora
$ make && make install

Convert

~/myvideos/dist/bin/ffmeg

But first, you need to tell where to find libraries:

export LD_LIBRARY_PATH=~/myvideos/dist/lib/

Here are my 3 command lines to convert to WebM, OGG/Theora and mp4:

• OGG/Theora

  ffmpeg -i input.mov   -acodec libvorbis -ac 2 -ab 96k -ar 44100   -b 345k -s 640x360 output.ogv
  

• WebM/vp8

  ffmpeg -i input.mov   -acodec libvorbis -ac 2 -ab 96k -ar 44100   -b 345k -s 640x360 output.webm
  

• MP4/h264

  ffmpeg -i input.mov   -acodec libfaac -ab 96k   -vcodec libx264 -vpre slower -vpre main   -level 21 -refs 2 -b 345k -bt 345k   -threads 0 -s 640x360 output.mp4
  

Hope it helps.

Look at the current version of html5test, the Forms part. Webkit has a good score (34/38, 89%), although their HTML5 forms support is incomplete (no UI, validity barely implemented, but they expose the input type). The way forms are tested is not that accurate: just testing if the input type is supported as a DOM property is not enough. The good way is to check that the constraint is actually applied (input.validity.valid).

//Exemple: testing <input type=email>
/*
 * How it was tested
 */
var valid = (input.type == "email");
/*
 * A better way to test it
 */
input.value = "foo";
var valid = false;
if (!input.validity.valid) {
  input.value = "foo@bar.org";
    if (input.validity.valid) {
      valid = true;
    }
}

I also added some tests for input.form, input.labels and label.control. I'm also testing the forms related CSS selectors (:required, :optional, :valid and :invalid).

I sent a patch to Neils. You can see the result here beta.html5test.com. Basically, webkit score is less good now for the forms section (29/45, 64%), but still better than Firefox4 ;) (and still very good for Opera).

Step after step, I'm building my blog engine :)

Honestly, I'm super excited to see IE9 coming with so many cool features. It's a little revolution :)

I just want to add one note to their awesome performance tests. When they test Firefox they don't activate the D2D acceleration in Firefox (and I understand that, we don't enable it by default, yet). But then, the result is a bit different...

DZ Slides.

But, seriously, guys, the Lenovo Shop is just the most awful online store ever. They don't know HTML links (just JS jumps), you get lost in like 2 minutes, it's a mess to understand the difference between all the products... well, a nightmare.

What about a sober but efficient design, like you do for your products?