# You can't --enable-big5 with aterm-0.4.2-ja.patch # I think it's very bad thing but as nobody complains it # and we don't have per-language flag atm, I stick to # use --enable-kanji/--enable-thai (and leave --enable-big5) These words should be thrown away since many chinese language speakers use FVWM-Crystal and thus use aterm. We need the support for Chinese! Reproducible: Always Steps to Reproduce: 1. Just read the ebuild 2. open an `aterm', it cannot display chinese characters even if -fm is correct 3. You cannot input chinese into it.
maybe a job for someone of the cjk herd?!
'Maybe'? No.. 'Definitely' - that's the word! :) Since I don't know a thing about this big5 stuff this bug seems to be about, I guess everyone will be better off if I reassign this to cjk :)
As I understand the comment, Big5 support can't be enabled once aterm-0.4.2-ja.patch has been applied. As we currently only have one USE flag (CJK) to support east asian languages, we have a problem there. Unfortunately I don't yet have an idea what can be done about it, but we'll see what can be done.
I just had a look at FreeBSD: they have two packages for this, aterm and zh-aterm. While this would be a solution to the problem, it doesn't feel like the "Gentoo way" (whatever that means) to me. I also found materm (now called mrxvt) which is based on aterm as weel as rxvt. It's available in portage and can do Big5 when linguas_zh_TW is set. Hope that helps for the time being, while we work on a proper solution for aterm.
is the zh-aterm just a patched aterm with some sort of chinese support? we can always take a look at that patch and see if there is some way to integrate it with the ja patch.
Why not set two ``use'' which are mutually exclusive, then apply appropriate patches. It is simple! Just like I manually apply patches and compile it.
@liquidx: Yes, I guess it's just aterm with a patch for Big5 support. Doing what you suggested was next on my list, but unfortunately I won't have time to have a look at it for the next few days (fsck university!)... @Yuan Mei: I guess we all agree that your solution would work, the problem is that the current ebuild uses CJK to apply the Japanese patch. Maybe it should use linguas_jp and linguas_zh_[TW,CN] instead, and apply either one of them.
I think it should use linguas_ja and linugas_zh_TW instead of cjk.
Split cjk USE flag into linguas_ja, linguas_zh_TW and linguas_th (Thai language support). It tries to use a font named "taipei16" by default (and cannot display big5 text), but if you specify correct big5 fontset it works fine.
