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,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4AC21CF7.6010405@cwilson.fastmail.fm>
Date: Tue, 29 Sep 2009 10:43:03 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
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: cygwin 1.7 has moved to utf8?
References: <h9t4k1$aqd$1 AT ger DOT gmane DOT org>
In-Reply-To: <h9t4k1$aqd$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Sven Köhler wrote:
> 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.

rxvt won't work well in the future with cygwin-1.5, unless you
explicitly set the encoding/charset to something like '$lang.ASCII' or
'$lang.iso-8859-1', I think. This is unavoidable, given that rxvt is
unmaintained upstream, and doesn't support the necessary constructs to
work well in modern i18n systems.

For X, use rxvt-unicode instead. For non-X, use mintty.  cygwin's plain
rxvt will continue to be maintained, but I expect its usefulness will be
limited on cygwin-1.7, especially for those who use $lang other than
'en_US' (even 'en_GB' will have difficulty on rxvt with the Euro and
Pound symbols).

> 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.

Things are still in flux, in cygwin-1.5.  See the current thread 'The C
Locale' on this list (go check the archive).  Also, there have been A
LOT of discussions about this over the past week on the
cygwin-developers list.
http://cygwin.com/ml/cygwin-developers/2009-09/

> 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?

Look at the cygwin-announce list, read the posts concerning the various
cygwin-1.7 beta releases, and follow the embedded links.
http://cygwin.com/ml/cygwin-announce/2009-07/msg00012.html
http://cygwin.com/1.7/cygwin-ug-net/ov-new1.7.html

And next time, look in the mailing list archives and the cygwin webpage
-- before asking questions that are prominently answered or discussed
already in these obvious places.

*However*, I admit that the most recent cygwin-1.7 test release
announcements (-52 ... -61) have not included the 'what's changed' link.

--
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