From mboxrd@z Thu Jan 1 00:00:00 1970 From: bachjh@googlemail.com (=?UTF-8?B?SsO2cmctSGVuZHJpayBCYWNo?=) Date: Sat, 13 Jun 2009 16:17:51 +0200 Subject: [sup-talk] sup and ncursesw In-Reply-To: <1244836517-sup-5520@entry> References: <91de50e10906101050p2d23a74cy1bbfe2e80e69cca2@mail.gmail.com> <1244836517-sup-5520@entry> Message-ID: <91de50e10906130717x3a6d6097g5249ed6bb17fbfcf@mail.gmail.com> 2009/6/12 William Morgan > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: