Description Martin Oberhuber 2008-08-18 05:43:19 EDT

For dstore connections, the remote encoding can be auto-detected (see bug 179937 comment 1). It's been a frequent problem for users where the locale of the remote host did not match the one of the local host, that they did not find out how to specify the remote encoding properly.

We should therefore try to auto-detect the remote locale by running "env" or "set" in a remote shell. Knowing the list of remote environment variables upfront would be helpful for other applications as well, e.g. knowing the remote host type (Unix, Windows, other) or shell type (bash, csh, Windows cmd) in order to run shell commands to find out the PID of a remotely started process (bug 161774), or set environment variables (bug 162018). Other applications such as WinSCP, for instance, do perform such shell-based discovery mechanisms.

Once a list of remote environment variables is known, the "LC_ALL" variable or probably others could be used. Other remote settigns such as the shell type, for instance, perhaps need to be stored in other places than the list of environment variables.