From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.165.135 with SMTP id k7cs18740icy; Wed, 24 Nov 2010 10:01:13 -0800 (PST) Received: by 10.224.19.203 with SMTP id c11mr8026019qab.170.1290621672887; Wed, 24 Nov 2010 10:01:12 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id my10si17774767qcb.33.2010.11.24.10.01.12; Wed, 24 Nov 2010 10:01:12 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 62E1119783B7; Wed, 24 Nov 2010 13:01:12 -0500 (EST) X-Greylist: delayed 360 seconds by postgrey-1.31 at rubyforge.org; Wed, 24 Nov 2010 13:00:45 EST Received: from lnx141.hrz.tu-darmstadt.de (lnx141.hrz.tu-darmstadt.de [130.83.156.236]) by rubyforge.org (Postfix) with ESMTP id BC98B1858376 for ; Wed, 24 Nov 2010 13:00:45 -0500 (EST) Received: from lnx500.hrz.tu-darmstadt.de (lnx500.hrz.tu-darmstadt.de [130.83.156.225]) by lnx141.hrz.tu-darmstadt.de (8.14.4/8.13.8) with ESMTP id oAOHwxvT010151 for ; Wed, 24 Nov 2010 18:59:00 +0100 (envelope-from neeb@kpvn.de) Received: from mailserver3.hrz.tu-darmstadt.de (lnx505.hrz.tu-darmstadt.de [130.83.156.234]) by lnx500.hrz.tu-darmstadt.de (8.14.4/8.14.4/HRZ/PMX) with ESMTP id oAOHsfVd001073 for ; Wed, 24 Nov 2010 18:54:41 +0100 (envelope-from neeb@kpvn.de) Received: from [130.83.253.17] (helo=[192.168.50.71]) by mailserver3.hrz.tu-darmstadt.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1PLJYH-0003qt-4Q for sup-talk@rubyforge.org; Wed, 24 Nov 2010 18:54:41 +0100 Message-ID: <4CED5155.3080502@kpvn.de> Date: Wed, 24 Nov 2010 18:54:29 +0100 From: Moritz Neeb User-Agent: Mozilla-Thunderbird 2.0.0.24 (X11/20100328) MIME-Version: 1.0 To: sup-talk@rubyforge.org X-PMX-TU: seen v1.0 by 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.11.24.174518 X-PMX-RELAY: mailout Subject: [sup-talk] ncursesw encoding X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hello everyone, William Morgan wrote: [sup-talk] System encoding versus messages encoding Tue Apr 22 19:18:00 EDT 2008 > 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. Is the suggested approach up to date? I am not really into git stuff, but I think the "next" repository is not in a state, that the commands below have the same effect than they had two years ago. Can you help me, to get this working? Is there another approach to get the message-encoding correctly displayed? -- Moritz Neeb _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk