Today’s Java puzzlement

Does anybody know why my CentOS 4.4 desktop system shows Korean fonts in both native apps (like gvim) and our Java application, but our CentOS 5.0 Theatre Management Systems (TMS) will only display Korean fonts in native apps. Obviously the fact that the TMS displays Korean fonts in gvim proves that the fonts are installed. And the fact that my CentOS 4.4 desktop shows the Korean fonts in our application proves that Java 1.5_011 can do Korean. Although the rpm names have changed, as far as I can tell the same Korean fonts are installed.

Anybody have any clues?

Dear Boss

Three years ago, when I was asked to implement a DocumentCache class in the cinlib, I made a mistake so that first build that had it was actually horribly slower than before it was implemented. Yes, I admit it. But I fixed that problem in the very next build, and it actually did end up being a net gain.

So is it really fucking necessary that every time since then when there the slightest question about cinlib performance, the first words out of your mouth are “can we try disabliing the DocumentCache to see if that fixes it”? I mean, it’s been three years. Give it up, already.

A stupid idea, stupidly done

In amongst my podcasts, iTunes downloaded three “PDFcasts”, two from Make Magazine and one from PilotCast. Of all the ways that people on the Internet have found to re-implement the same basic idea as Usenet, this has got to be the worst. If I wanted content that I had to read on my computer, what’s wrong with a web page? Or better yet, an RSS feed for a web page. Or an email list. Or Usenet.

Ok, that’s one thing

I discovered why OpenID comments went from working some of the time to working never: last time I upgraded my blog I’d inadvertently made it so none of the directories within my blog site were writable by the web server, and the OpenId plugin makes temporary files. That lead to the discovery that as well as OpenID comments, the directory used by the Gravatar cache wasn’t writable, which lead to the discovery that the Gravatars weren’t updating at all, even after I fixed the permissions, which lead to the discovery that when the Gravatar plugin discovers it can’t write to the Gravatar cache directory it just silently turns the “Enable caching” option to off, which lead to the discovery that even when I turned it back on, it still wasn’t updating, which lead to the discovery that there is an option in the plugin to “Use REST protocol” which evidently Gravatar doesn’t support any more so I had to turn that off. Phew. Now Gravatars seem to be working again.

Knees still hurt like hell, though.

META: Don’t use OpenID

OpenId comment authentication seems to be extremely hit-or-miss. It works for some, and for others their posts get flagged as spam, and for others still they get swallowed entirely. I’ve tried to debug it, but I haven’t figured out what’s wrong. I tried to deactivate it, but it just made things worse. So until further notice, please don’t use OpenID or your LiveJournal ID to comment on here.

Update: I just remembered that I had to hack the source in order to make this work before, and I recently installed an update. The update probably over-wrote my hack. Now to dig though the backup to see if I can find the hacked file.