X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: =?ISO-8859-15?Q?Sven_K=F6hler?= Subject: cygwin 1.7 has moved to utf8? Date: Tue, 29 Sep 2009 16:12:17 +0200 Lines: 22 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.23 (X11/20090828) X-IsSubscribed: yes 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 Hi, is it just me, or does cygwin 1.7 return a utf8 encoded strings for filenames and the like? I wonder, because rxvt and xterm show two strange characters for each german umlaut when I use "ls -la" or the like. Well, I don't think that rxvt will ever work, because it doesn't support unicode. And there doesn't seems to be a non-X11 version of rxvt-unicode. But I would expect, that xterm works. But it doesn't. The default-encoding, that cygwin returns, seems not to be utf8. I have didn't experiment with setting the LANG variable yet. I'm curious what going on and how the upcoming cygwin 1.7 will be like. Is there some information about it on the net? Regards, Sven -- 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