New site: A War of Choice

Be sure to check out a site I did for Jack Fairweather’s book, A War of Choice, about the British in Iraq:

It features a central “stage” for various media assets — sliding promos, photos and a gallery.

Japan tsunami disaster poster – (東日本大震災ポスター)

I made this poster to commemorate the tragic devastation in Japan in March 2011:

Help Heal Hope: Japan tsunami disaster poster

Japan Tsunami Disaster Poster

  • HELP すくい (sukui)
  • HEAL いやす (iyasu)
  • HOPE  のぞみ (nozomi)

with logos for Iwate, Miyagi and Fukushima prefectures which suffered the bulk of the destruction.

In memoriam, 2011.03.11

Download the pdf here (350kb)

Feel free to share or use this graphic to aid Japan (creative commons license)

HDTV screen protector hack

Anyone with kids knows:

children + flat-screen TV = expensive disaster waiting to happen

Yet manufacturers somehow put very soft screens on TV nowadays, instead of something more durable like glass. There are a few products out there for protecting your TV but I found them a little expensive. Instead of waiting for big toy-shaped dents in our new LCD, my solution was to get a sheet of acrylic at an art store, drill out flat slots, and attach it using long velcro strips which thread the slots.

A few details:

  • Our 32 inch TV just happened to be about the dimensions of a 24″x36″ sheet, which at 1/8 inch was $20. Maybe a  quarter inch could stop a brick, but an eighth inch is enough to deflect most projectiles and keep peanut butter off the LCD surface. (For larger sheets, Home Depot might be an option.)
  • Long strips of Velcro are a few bucks at a hardware store. I wrapped it from the top and bottom around the back. The upper part sticks to the lower part, so there is no glue or anything on the TV itself. It has enough surface area to hold the acrylic sheet.
  • Drilling the slits was a bit tricky and I admit I did a poor job of it — not perfectly flat, but a little bumpy. Maybe somebody has a better technique or tool for creating the slots.
  • The acrylic sheet bows a little. But it is hard to tell from the front. It also gets a little staticky. To clean, I would take the whole thing off and wipe it. Wiping only the front seems to attract dust to the back because of static.
  • As for glare, it has a glare when the TV is off, more than the matte finish of a typical LCD. But with the TV on, you can’t see the glare.

So far it has worked well and saved our TV from several bumps. Take a look:

Tragic sans

If Comic Sans could talk ….

You think I’m pedestrian and tacky? Guess the fuck what, Picasso. We don’t all have seventy-three weights of stick-up-my-ass Helvetica sitting on our seventeen-inch MacBook Pros.


Sorry I’m standing in the way of your minimalist Bauhaus-esque fascist snoozefest. Maybe sometime you should take off your black turtleneck, stop compulsively adjusting your Tumblr theme, and lighten the fuck up for once.


People love me. Why? Because I’m fun. I’m the life of the party. I bring levity to any situation. Need to soften the blow of a harsh message about restroom etiquette? SLAM. There I am. Need to spice up the directions to your graduation party? WHAM.

While Avenir is practicing the clarinet, I’m shredding “Reign In Blood” on my double-necked Stratocaster. While Univers is refilling his allergy prescriptions, I’m racing my tricked-out, nitrous-laden Honda Civic against Tokyo gangsters who’ll kill me if I don’t cross the finish line first.

New site:

Just wanted to mention my latest personal project,, a Japanese Kanji dictionary (a complete listing of 2000+ characters) in blog format. Essentially, I used the WordPress publishing format to enable me to maniupate PHP to give me a unique web application.In other words, a dictionary-blog mashup.

Unconventional? Perhaps. But give it a try. Students of Japanese language will certainly find it useful.

(Hint: The top page is randomized, so if you bookmark it or set it as the default browser page, you’ll get some new kanji each day)

HTML 5: first impressions

While there’s been talk for some time about the future of HTML, including debates over XHTML 2.0, semantic web, and the like, the latest release of Firefox makes it more concrete by actually including some HTML 5 support. So I’ve been reading up on it a bit, and while it will fill in some holes — video support! — overall it seems somewhat muddled and disappointing.

Now we’re going to add all sorts of “semantic” items like nav, header, article, footer, which will absolutely not be compatible with older browsers.  (This ensures that  it will take years before it is considered “safe” to use. Pages such as this break in browsers as new as IE8!)  How exactly is this an improvement upon existing use of DIVs with class and id? You can use your DIV in any way you wish to accomplish all of these things. If a standard nomenclature was needed (like Dublin Core), that could have been standardized, as in <div id=”nav”> <div id=”header”> and so on. This works today.

The user will never see this anyway, and search engines could easily understand the semantic nature of these divs, since just about everyone uses the same names! (That was supposedly the basis of the research proposing these — they were drawn from he most commonly used div names) Google could easily — today — treat anything with an ID or class of “nav” as a navigation. Heck, it probably already does. So where’s the benefit for these major changes to the most widely-used document standard in the world? I’m not seeing anything that couldn’t have been achieved in other ways.

A while back, A List Apart had some suggestions for adding extensibility while preserving backward compatibility using attributes. (Ex: <div structure="header">) These were duly ignored. But the introduction is worth repeating:

I’m going to make a bold prediction. Long after you and I are gone, HTML will still be around. Not just in billions of archived pages from our era, but as a living, breathing entity. Too much effort, energy, and investment has gone into developing the web’s tools, protocols, and platforms for it to be abandoned lightly, if indeed at all.

Let’s stop to consider our responsibility. By an accident of history, we are associated with the development of an important tool our civilization will use to communicate for decades to come. So, when we turn our minds, idly or in earnest, to improving HTML, we must understand just how far-reaching the ramifications of today’s decisions may be.

This also seems a step back to the bad old days of font tags, b, i, etc. These were not only presentational, they were also not extensible or flexible. Class and ID enable great flexibility, so that new techniques can be developed and sites can be changed easily from a central style sheet. Now we are back to an array of one-trick ponies that are hard-coded into the HTML. And we will add more in coming years, which will also break compatibility.

Headings and sections

And then there’s those sections:

  <h1>Level 1</h1>
    <h1>Level 2</h1>
      <h1>Level 3</h1>

Maybe I am missing something, but the current usage of h1, h2, h3, h4, h5 and their child paragraphs are equally structural, giving clear hierarchy. Is it really better to only use h1’s in nested sections, rather than the less verbose use of numbered headings?:

<h1>Level 1</h1>
<p>Level 1 content</p>
   <h2>Level 2</h1>
   <p>Level 2 content</p>
      <h3>Level 3</h1>
      <p>Level 3 content</p>

Even the video element, which I welcome, might be messy: Is it clear that everyone will switch to OGG or Vorbis or whatever the spec says? All we need now is Microsoft and Apple strong-arming everyone to push their video formats as the standard. Isn’t this why Flash video took off in the first place — because it bypassed the OS makers video format wars?

So, is HTML 5.0 a consequence of the latest round of browser wars? Perhaps the rush to beat the competition has pushed Firefox, and soon the others, to rush into HTML 5.0 without adequate thought.

Also, is this a case of browser and OS makers strong-arming the W3C into making HTML a friendlier place for their web apps, rather than the ideal that the users, coders and designers would have wanted?

Many of the fixes in HTML 5 seem to solve non-problems. It is also not future-proof or extensible. In 5 or 10 years, they will need to add entirely new elements, and remove some older ones. So we are stuck with never have a truly extensible standard that is backward and forward compatible.

I’m not against progress, but I think they could have done better than this.