Reformatted excerpts from Israel Herraiz's message of 2008-04-21: > As far as I know (considering what I have read in the documentation > and in the archives of this mailing list), Sup determines the encoding > using the environment variables and tries to decode all the messages > using that encoding.
This is not correct. Sup DOES determin the message's (or MIME component's) charset, and transcodes it to your terminal charset using the iconv library before display. (After decoding quoted-printable, etc.) The problem is actually that the Ruby ncurses gem is not wide-character aware, so dumping UTF8 to the terminal doesn't actually work. Well, it actually does seem to work for some characters, but not most of them. The solution has been known for quite some time, but it ain't pretty: http://rubyforge.org/pipermail/sup-talk/2007-October/000297.html The good news is that I've just made it slightly simpler, at least if you're running from git. I've published an "ncursesw" branch that contains a hacked ncurses-0.9.1 and a dirty script to install it into your ../lib/ directory. If you use that AND you run from git next, you'll see wide characters. It works! So, just a "few" "simple" commands: $ git branch --track ncursesw origin/ncursesw $ git checkout ncursesw $ cd ncurses-0.9.1/ $ ./run-this-for-sup.sh $ cd .. $ git checkout next $ ruby -Ilib bin/sup ... and you should see wide characters, assuming your terminal is capable. If make dies, you probably need to install some kind of ncursesw development library. On my Debian system it's a package called libncursesw5-dev. A gold star to anyone who makes a nice wiki page out of this. -- William <[EMAIL PROTECTED]> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
