This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [1.7] Updated: cygwin-1.7.0-45


On Apr  2 16:30, Thomas Wolff wrote:
> [Should I have responded to cygwin-announce? Not sure.]

Definitely not.

> Corinna Vinschen wrote on cygwin-announce:
> > 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,

Baaeh.  That's one aspect I didn't realize when I made this change.
Does that really mean we have to keep codepage:foo just for the sake
of the Windows console window?  Does anybody have any other idea?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]