X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_83
X-Spam-Check-By:	sourceware.org
Date:	Thu, 2 Apr 2009 16:30:56 +0200 (CEST)
Message-Id:	<200904021430.n32EUuKv024760@mail.bln1.bf.nsn-intra.net>
From:	Thomas Wolff <mined AT towo DOT net>
To:	cygwin AT cygwin DOT com
Subject:	Re: [1.7] Updated: cygwin-1.7.0-45
References:	<20090331111757 DOT GA22043 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20090331111757.GA22043@calimero.vinschen.de>
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

[Should I have responded to cygwin-announce? Not sure.]

Corinna Vinschen wrote on cygwin-announce:
> Hi folks,
>
>
> I just uploaded a new Cygwin 1.7 test release, 1.7.0-45.
>
> ...
>
>
> What's new in contrast to 1.7.0-44
> ===================================
>
> - A lot of character sets are supported now via a call to setlocale().
>   The setting of the environment variables $LANG, $LC_ALL or $LC_CTYPE will
>   be used.  For instance, setting $LANG to "de_DE.ISO-8859-15" before
>   starting a Cygwin session will use the ISO-8859-15 character set in
>   the entire session.  UTF-8 is supported as well, as in "en_US.UTF-8".
>
>   Along these lines, the "CYGWIN=codepage:{ansi,oem}" setting has been
>   removed in favor of using $LANG, $LC_ALL, or $LC_CTYPE.
>   
This is a great step. However, there is a problem. Until 1.7.0-44, the 
terminal encoding was maintained transparently into a remote session,
so that if you rlogin somewhere else, you would have the same encoding as
configured in the cygwin console. This worked nicely with all three 
available encodings, the default (CP1252), codepage:oem and codepage:utf8.
(For most situations, you would still have to set LC_ variables explicitly 
on the remote system; well, most remote systems would not have CPxxx 
locale data but that's a different issue.)

Now with 1.7.0-45, after remote login, the encoding is always just 
ISO-8859-1, while of course, if I have a UTF-8 terminal, I want to take 
this over to the remote system. Maybe it's some interworking problem 
with the new cygwin dll and the old rlogin.exe?
Until 1.7.0-44, even something like the following worked:
Inside a default cygwin console (or a codepage:oem) console, you could type
	CYGWIN=codepage:utf8 rlogin ...
and get a UTF-8 remote terminal environment. Now, no attempt to 
establish that seems to work anymore.

I would appreciate if this can be resolved,
Kind regards,
Thomas

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -