2009/6/12 William Morgan <wmorgan-...@masanjin.net> > > What is your environment's character set? (Should be the first line of > output logged by Sup.) What is your terminal emulator? And what's the > behavior without the patch to ncurses.so?
After playing around a bit i think the behaviour might be related to a problem with locale. I reinstalled ruby, rubygems, ncurses and sup. No patch to ncurses this time. Using gnome-terminal or xterm with "TERM=xterm" now lets umlauts etc look like, e.g. "JM-CM-6rg-Hendrik"). The reported character set is "utf8". The same happens when using urxvt with TERM=rxvt-unicode. However, calling sup like this: $ LC_ALL=en_GB.iso-8859-15 sup results in different behaviour in the two emulators: xterm looks OK when viewing the inbox, but inserts boxed question marks in thread-view. rxvt-unicode displays everything correctly, but drops the last character of a line when a non-ASCII element is somewhere in the line. In both variants sup reports the character set correctly as iso-8859-15. So I guess I could simply work in urxvt and that's OK, then. Do other widechar ncurses programs work? The only other ncurses-based program I am aware of using is midnight commander, and it seems to be working fine. But I don't know whether it uses the widechar variant. cheers, - Jörg-Hendrik
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
