25 Jan 2004 noda   » (Journeyer)

Who needs the W3C validator?

If your answer is "everybody," you're wrong. It's now "everybody but Epiphany users who've installed OpenSP development headers (and libraries) and a CVS (today or newer) checkout of Epiphany Extensions."

Yes, I've coded what everybody needed but didn't realize: HTML validation built into the web browser. Not only does it display the same output as w3 would, but it validates locally -- which means it's much faster and it works on all pages you can browse to (no problems with cookies, https or localhost; no saving to file and uploading; no privacy concerns). It's like... your very own w3 validator. And it looks pretty.

Temporary problem: it only works on XHTML... or something along those lines. Now I've got to make it work for all the pages w3 does, which shouldn't be hard because the w3 validator is open-source.

"But wait," you say. "I use W3 because I can trust it's correct. How could your extension ever be as accurate as W3?" And there's a simple answer: because it uses the same backend as w3 (OpenSP). As soon as I make its frontend set the same parameters, it will have exactly the same output. For now, UTF-8 XHTML is validated identically. When I'm less lazy, I'll finish the job.

In short, I've coded something very Cool and Original. And that makes me Proud.

Latest blog entries     Older blog entries

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!