> I was going to add the fact that telnet, rlogin, ssh etc should pass along
> the LANG and LC_* variables like they do DISPLAY and USER but then I read
> the other messages ...
>
Be careful about making too many assumptions about how Telnet is being used.
There was once a Telnet CHARSET option proposal, which was a very bad idea
for the same reason. Users should be able to make their Telnet clients
adapt to any character set used by the host, if they want to. They should
also be able to transfer files, e.g. with Kermit or Zmodem, over the
Telnet connection, use terminal-oriented graphics protocols, and who knows
what else, so nothing should should happen to anything the host sends until
the Telnet client gets it.
As long as we have a plethora of character sets, we have to keep control in
the hands of the end user, i.e. the user of the client. We don't want
various agents along the communication path making conversions based on
guesses about the encoding or behavior of the files or applications involved.
- Frank
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
