On Apr 2 16:59, Corinna Vinschen wrote:
> On Apr 2 16:30, Thomas Wolff wrote:
> > > removed in favor of using $LANG, $LC_ALL, or $LC_CTYPE.
> > >
> > [...]
> > 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?
These are the choices we have, afaics:
1. Use a "CYGWIN=codepage:foo" look-alike which only sets the console
charset.
Pro: Console codepage is easily determinable.
Con: Yet another environment setting which can go wrong.
2. Use the environment variable setting of LC_ALL/LC_CTYPE/LANG at
the moment the console is opened the first time and then never
change this setting again until the console is closed again.
Pro: Only one environment variable has to be set for the
internationalization (which was the intent of the original patch).
Con: The variable must be set before starting a Cygwin console.
(But that's better the case anyway, as explained in
http://cygwin.com/1.7/cygwin-ug-net/setup-locale.html#setup-locale-problems)
3. Change rlogin to call setlocale(LC_ALL, ""); at the start of
main.
Pro: Cygwin doesn't have to be changed.
Con: Inetutils has to be changed. But the setlocale call would be a
good idea anyway, probably.
Con: OpenSSH has the same problem.
Con: The problem persists for all applications which don't set
the locale. OTOH, this only affects remote connection apps.
Solution 3 seems not feasible. I'm leaning towards solution 2. Does
anybody know a reason why we should prefer solution 1? Does anybody
have another solution?
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/
