Log in

No account? Create an account
22 May 2008 @ 08:20 pm
Ruby::Tk is really pissing me off.
In the mood: aggravatedaggravated
Dustybigmog on May 23rd, 2008 01:28 pm (UTC)
*Tickle tickle tickle*
Douglas Triggs: bad icondoubt72 on May 23rd, 2008 10:18 pm (UTC)
It's not the TCL. There is no TCL. It's the TK!

Totally choking on the the UTF8, and all I'm trying to do is render tone diacriticals.
donaldmarino on May 24th, 2008 01:32 am (UTC)

Use Ruby GTK, it has pango and does many char sets with aplomb.
Why use Tk?

Douglas Triggs: languagedoubt72 on May 24th, 2008 06:43 am (UTC)
Because I already wrote my Japanese drill tools in Ruby::Tk, and just wanted to make "quick" modifications instead of rewriting things from scratch (which, admittedly, once I gave up on it working correctly and hacked around it, really were fairly quick modifications).

But, yes, I was pretty damned tempted to dump it completely.

It's quite possibly as much Mac OSX's fault as Tk's, there's some not playing well with others involved, I suspect (because, interestingly enough, everything worked just fine as long as I stuck with Japanese characters, even though it's all the same CJK unified code pages).