I’m playing with my old Sony XG-19 again. As reported earlier, OpenBSD 4.1 worked but never played DVDs, Fedora 7 blew chunks during the install, and Debian 4.0 worked fine, requiring only a few xorg.conf tweaks and a copy of libdvdcss2.

But it sucked for Japanese, so it had to go. There are all sorts of input managers and applications available, but they don’t all play nice with each other, and the system setup assumes that anyone who wants to type in Japanese wants a completely localized system. You can work around this, eventually, but I lost patience.

So I tried CentOS 5. The graphical install worked fine, the xorg.conf file only needed a one-line change to shut off double-tapping on the trackpad, and once you find DAG, it’s easy to get DVDs playing with VLC (Totem steadfastly refuses to admit which of its plugins are missing, and nothing I install seems to placate it, but who cares?).

The Japanese support in CentOS is much more mature, and offers a user experience reasonably close to Mac OS X or Windows. The default keybindings are naturally different from anything you’ve ever used before, but one has to make some concessions when dealing with Open Source, and it has a “behave like Windows” option.

Now to build the current version of Claws Mail…

[Update: got Claws 2.10 built and running, and unlike my Debian install, it plays nice with the Japanese input method.]

Our product is no longer a secret. Most of the tech blogs and news sites have something up today, although the quality of information varies. I won’t be commenting on it here much.

I’m still plugging away at my kanji study, mostly using Kakitorikun for the DS. Since it’s intended for Japanese children, I’ve gotten used to looking up vocabulary related to baseball, school life, and traditional culture, but I still run into trouble occasionally. Sometimes I stop and figure these oddballs out right away, but this one sat on a post-it note for a week before I finally got back to it:

Hint：む色半とう明の細長いちいさなさかな。
Ｑ：白魚。
Ａ：◯◯◯◯

The answer is しらうお. I knew the answer had to be a kind of fish, and I knew it was a long, thin, small fish, but even if I had correctly parsed mushoku-hantoumei as “colorless, half-transparent”, I wouldn’t have known which fish, because I don’t know anything about Japanese fish. Not even the ones you find in sushi bars.

The teaser trailer for the new Get Smart movie should have spent a lot less time on Max, and a lot more time on 99 (Anne Hathaway). Or 23 (The Rock). Or the Chief (Alan Arkin). Or even the empty phone booth (uncredited), because the actor they cast for Max just doesn’t have it.

The 250GB drive for my MacBook arrived, and with two fresh backups in hand (plus a third on the old drive), I quickly installed it. It was completely painless to migrate my Mac environment over. You can do it half a dozen different way for free; I chose SuperDuper.

But I also have a Vista partition on this machine, and Vista (if you bought the right version) includes a Complete PC Restore tool that’s designed specifically for moving a complete, working installation onto a new disk… as long as you don’t mind the risk of spending half an hour on the phone reading authorization codes to someone in India to reactivate it.

The old disk had 124GB for Mac, 25GB for Vista. The new disk had 185GB for Mac, and 47GB for Vista. After finishing the Vista restore, both partitions booted correctly, so I went ahead and activated. Then I checked the free space, and found that Vista was still only using 25GB.

No problem, thought I. It’s trivial to extend an NTFS partition into the remaining free space, so I opened up the relevant tool, and found the original partition sizes, with an empty 80GB partition at the end of the disk.

fsck and chkdsk both insisted that the volumes were valid from their respective OS’s, but on the Mac side, it thought the Vista partition had a lot less files in it than it should have. Not good. Very, very not good.

Not being an idiot, I started over, rebuilding the disk from scratch again. Since it’s a Mac, I just booted the old drive from an external FireWire enclosure and ran SuperDuper again. This time, though, I didn’t bother using the Vista restore tool; I just dd’d the old partition over and ran the repair tools from the install CD. I still need to do an upgrade install to clean up the boot files, resize the filesystem to fill the new partition, and then reactivate again, but it should work this time.

There’s actually a checkbox in the Vista Restore process that theoretically allows you to restore onto an existing partition without trashing your new disk, but it was grayed out, and clumsily worded. Net result: one of the features you pay extra for in certain Vista versions is not only useless, but dangerous.

In a rare example of good sense, though, you can get at all of the data in the backup; it’s a disk image in VHD format.

No, not that one. Or that one. Or, well, anything you were planning to see this summer.

I mean this one, with an HD trailer that’s so far away from the original teaser that they must have spent weeks assembling it from spare footage.

Some dolt is spamming Japanese-study forums with a link to their online test site, emanabu (no link from me!). The sample tests are riddled with errors, and many of the sentences are just painful. I particularly liked the question where they thought “amari samuku arimasen” meant the same thing as “totemo atsui desu”.

Restoring Chizumatic‘s sidebar to its rightful place was a task worth pursuing, but since the Minx templates generate tag soup, standard validation tools produced too many errors to help much (W3C’s produced ~700 errors, compared to this page’s 16, 14 of which are parser errors in Amazon search URLs).

So I tried a different approach:

#!/usr/bin/perl
while (<STDIN>) {
    chomp;
    next unless /<\/?div/i;
    if (@x = /<div/gi) {
        print "[$l] $. ",@x+0," $_\n";
        $l += @x;
    }
    if (@x = /<\/div/gi) {
        print "[$l] $. ",@x+0," $_\n";
        $l -= @x;
    }
}
print "[$l]\n";

Skimming through the output, I saw that the inline comments started at level 6, until I reached comment 8 in the “Shingu 20” entry, which started at level 7. Sure enough, what should have been a (pardon my french) <tt></div></p></div></tt> in the previous comment was just a <tt></p></div></tt>.

[Update: fixing one bad Amazon URL removed 14 of the 16 validation errors on this page, and correcting a Movable Type auto-formatting error got rid of the other two. See, validation is easy! :-)]