Holizz versus the Web

一昨日、またダイアログを録音しました。

私が「母の金魚が死んでしまいました。」と言って、他の人が「わたしのすきないろはみどり。あなたは？」と言いました。

私がそんなに笑っちゃっていましたから録音をとめなきゃでした。

あのせりふの後で「好きな色はむらかみです。」と言いました。

と言うわけで、大成功でした。

Well due to the lack of locale support, I evidently can’t use OpenBSD as a desktop system. I have, however, been running OpenBSD as a server (SSH-able NAS, MPD-able music). It’s a joy to administer, and I’ve just worked out how to set up the default chrooted Apache to serve my klookup project. See 10.16 - Tell me about this chroot(2) Apache?, the trick is copying over the Ruby binaries and libraries into the chroot jail, and the linked libraries with the help of the ldd command.

I was implementing UTF-8 in the tree of klookup until half past midnight last night. It wasn’t even something necessary to the project, but it was fun. I could do with investigating alternatives to what I’m doing. Like writing some Ruby extensions in C, or using Unihan (which is significantly bigger than KANJIDIC, but doesn’t require testing each character’s codepoint to see if it’s kana).

I talked to somebody at Acer, and they said that they sell the laptop and the OEM software as a package and so I can’t return my OEM copy of Windows XP (which I already deleted).

The EULA I downloaded from microsoft.com says “IF APPLICABLE”, and was not for an OEM distribution, or even for the correct distribution of Windows XP. So Acer and Tesco are probably within their rights to not refund me.

At least I tried, and gained telephone XP in the process.

Well I haven’t written much about this, but I’ve spent many hours on it.

My final year project is a multiradical kanji lookup tool, in Ruby.

Just yesterday, KLookup was approved for inclusion on RubyForge.

So now you can check out the source:

svn checkout svn://rubyforge.org/var/svn/klookup

If you don’t like or have Subversion, I have already made a release.

Supposedly it will run (the executables can be run when in the bin/ directory - note that gklookup does nothing) and install (beware of setup.rb’s weird behaviour). Its only dependency should be Ruby (cklookup requires readline, but falls back to gets). Also, klookup.cgi (drop the whole directory into a directory with ExecCGI set) is apparently confusing, so just bear with it for the moment.

Suggestions, fixes, and questions are very welcome. My email address is floating around somewhere on this site, it’s foobar__AT__holizz.com, where foobar is any string you like.

緑帯になったんです！ぼうもパッスしました！

I became a green belt. I also passed bou (quarter staff).

Tom’s untopical tip: put a “TODO” in your source tree at every point where you have an actionable (make a central file for those without a place). Then you can grep -R TODO * | wc -l to check the general status of the project.

Turning up the font size on GNOME Terminal, removing the menu bar, and hitting F11 (obviously the first two steps are in the configuration).

It’s better than using a virtual terminal because black screens seem to reflect more and Ubuntu’s console doesn’t have Japanese fonts (as they say, X’s true purpose is higher resolution fonts).

P.S. I think I ate a cursed carrot of hunger today. In the end I decided to resurface with my trusty steed and without the Amulet of Yendor. I’m getting better at nethack, but my problem is that I have more important things to do. Maybe that isn’t a problem.

Because I needed to get something working in Ruby (I’m prototyping), I’ve been testing the same thing in various languages.

My project (multiradical kanji lookup - it doesn’t have a name yet) will probably take its input directly from radkdict. As a result, each line contains many kanji, so I decided to just split(//) on each line that I needed. ちょっと待て〜！ Just doing that gives me a list of the bytes in the file, not a list of the characters. There’s no practical difference in UTF-8 between bytes and characters before you get a fair way away from ASCII, but when you’re looking at characters from the Han block there’s three bytes per character but rules of thumb are not the sort of thing you want to base parsing a text file on.

To cut a long story short, if you set $KCODE to ‘u’, splitting using RegExps will work (but indices still won’t).

So Ruby is FTL (for the loss, not faster than light). I’ll probably still be using Ruby for the project despite its failings. I haven’t even started on the background research (next: other research, analysis, design, and the development is where I start on the non-prototype code), so I still have plenty of time to change my mind.

Python (2.5, of course) and Perl also suffer the same sorry substring stupidity.

Java, on the other hand, works perfectly with substrings. The usual String.substring method works perfectly. When I ask for the first two characters of “英語が話せますか”, it gives me “英語”.

For the past few years Java has been growing on me. Now I’m really starting to think it’s a good thing. I’m looking forward to the day they open source it. gcj/gij are pretty good, but they’re not quite compatible yet.

I noticed jython in Ubuntu’s universe today so I installed it (no JRuby yet). It’s pretty damn swanky, despite the fact that jythonc depends on Python 2.1 (which is over four years old) - so I can’t compile Python classes to Java bytecode. It’s pretty good. You can evaluate Python from Java and access Java classes from Python.

Stream of conciousness journal entries FTW. Splat.

IMEs are the best invention in the world. This week I’ve typed Ï€ and done some box drawing without having to look at 文字マップ (Gucharmap in this case).

Today I learnt Ï€ to 9 digits thanks to the Japanese language and this post. It was HARAGUCHI Akira’s recent escapades into real numbers that made me want to find Ï€ in Japanese phrases. It’s a great language for memorising numbers.

Today I have also been looking at fun things like graphical toolkits. It’s hard to put into words why GTK+ 2 could beat Qt or Tk in a fight. Just say that GTK+ 2 has a wider deployment and hope for the best. And then try to think up a good reason to choose Ruby over Python (I don’t think “Ruby is more Japonz” will cut the mustard in final year project documentation).

I shall probably start some coding of that soon (maybe sooner than my Gantt chart tells me I should be doing - but I’m sure I’ll live).

Well. I should go to bed now so I can go swimming in the morning and then write lots and lots of documentation.

P.S. I subscribe to the Doctor Will documentation methodology: have everything in a wiki then just print it out and call it a report.

本当によかったと思う。It really finished the series off nicely. It’s a shame there won’t be any more (until the 電車男 SUPER DX MEGA SPECIAL) because I loved the series so much. 電車男のドラマと愛していた。

OMFG! It supports everything! I nudge-flooded everybody. Then I got bored of it.

Yes, I’m treating my normal blog as a sideblog now. Long posts are for people with free time. いそがしいよ！