X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SARE_SUB_ENC_UTF8,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B1E50BA.7070908@cwilson.fastmail.fm> Date: Tue, 08 Dec 2009 08:12:26 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: UTF-8 in Cygwin console on 1.7 References: <4B1E4D22 DOT 9020406 AT hones DOT org DOT uk> In-Reply-To: <4B1E4D22.9020406@hones.org.uk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Cliff Hones wrote: > [I was rather surprised to discover that non-X rxvt does not handle > UTF-8 output at all, not that this causes me any great concern.] rxvt is dead, upstream, and will never support anything but narrow characters. I'm seriously considering marking it _obsolete sometime after cygwin-1.7.1 is released. Use mintty for non-X, and rxvt-unicode for X. I'll even release a run2-style xml configuration so that you can mimic the "dual mode" nature of current rxvt with those two programs. -- Chuck -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple