Re: japanese with devel mutt
On Sun, Nov 12, 2000 at 04:36:37PM +0800, Anthony Liu wrote: OK here is my take: There are two xterms you can choose to display Japanese character set. However I have only tried the more popular shift-jis encoding, which the other one is deprecated, I think. One is Kanjiterm, Kterm in short. However, it is a bit hard to find. The other one is Aterm, which is called the Afterstep Term. You have to compile Aterm with somthing like "--enable-kanji" with configure. Once you have it compiled. Start Aterm, fire up lynx and load the page "http://www.yahoo.co.jp/". Notice: lynx support for Japanese and Chinese encoding is a bit broken. Enlightened Term (Eterm) said to support Kanji (which is a bad description), I have yet to get it to work, you might need to set the locale variables. However, if you use emacs, you should try out MULE, which is a multi-lingual edition for emacs. If you want X apps to display Japanese, there are more you have to do then just the xterm. This isn't my problem. I'm using rxvt built with kanji support -- the problem is that mutt only displays the characters properly if I set the LANG environment variable. kanji support is working great in the term, I just need to convince mutt to display it properly. Perhaps I'll try rebuilding xterm with unicode support :) ttyl, -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A PGP signature
Re: japanese with devel mutt
On Sat, Nov 11, 2000 at 09:40:18PM -0500, Josh Huber wrote: I'm trying out mutt version 1.3.11i, mostly because it has support for automatically switching the charset= line in outgoing emails to the proper encoding. Here's the problem: I can't get japanese to display properly without using something like LANG=ja_JP /usr/local/bin/mutt, which causes subprocessies (like gpg) to run with that language envionment. I'd like it to display text without setting the LANG variable, so I looked at the charset variable, and tried setting it to iso-2022-jp, which didn't seem to do anything, except prevent me from viewing japanese text. (of all things) am I clueless here? anyone have hints on how to set this up? I'm using xemacs with canna for input/sending email, btw. also, is this the proper place for these questions? people on -dev might have a better idea :) thanks in advance, OK here is my take: There are two xterms you can choose to display Japanese character set. However I have only tried the more popular shift-jis encoding, which the other one is deprecated, I think. One is Kanjiterm, Kterm in short. However, it is a bit hard to find. The other one is Aterm, which is called the Afterstep Term. You have to compile Aterm with somthing like "--enable-kanji" with configure. Once you have it compiled. Start Aterm, fire up lynx and load the page "http://www.yahoo.co.jp/". Notice: lynx support for Japanese and Chinese encoding is a bit broken. Enlightened Term (Eterm) said to support Kanji (which is a bad description), I have yet to get it to work, you might need to set the locale variables. However, if you use emacs, you should try out MULE, which is a multi-lingual edition for emacs. If you want X apps to display Japanese, there are more you have to do then just the xterm. Anyone would like to comment further?
japanese with devel mutt
I'm trying out mutt version 1.3.11i, mostly because it has support for automatically switching the charset= line in outgoing emails to the proper encoding. Here's the problem: I can't get japanese to display properly without using something like LANG=ja_JP /usr/local/bin/mutt, which causes subprocessies (like gpg) to run with that language envionment. I'd like it to display text without setting the LANG variable, so I looked at the charset variable, and tried setting it to iso-2022-jp, which didn't seem to do anything, except prevent me from viewing japanese text. (of all things) am I clueless here? anyone have hints on how to set this up? I'm using xemacs with canna for input/sending email, btw. also, is this the proper place for these questions? people on -dev might have a better idea :) thanks in advance, -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A PGP signature
