Ah, bugger, my fault. Generating en_US.UTF-8 and setting LANG to en_US.UTF-8 worked.
Perhaps openssh should display a warning or fall back to a working configuration if LANG is not set to a workable value? Currently it just makes the console unusable if the settings are not correct and I try to write a non-ascii char. Thanks! Regards, Thue On 10/11/06, Colin Watson <[EMAIL PROTECTED]> wrote:
On Mon, Oct 09, 2006 at 05:30:20PM +0200, Thue Janus Kristensen wrote: > When ssh-ing into another machine, I am able to write Danish > characters such as æ,ø,å ( http://en.wikipedia.org/wiki/%C3%86 , > http://en.wikipedia.org/wiki/%C3%98 , > http://en.wikipedia.org/wiki/%C3%85 ) > But they are not displayed correctly, the console becomes messed up. > > The problematic characters work fine on a local console. They also > work fine when ssh-ing into the same server from Windows using putty. > > $LANG on my local machine is en_US.UTF-8. When logging in via ssh > $LANG is initially empty, but setting it to en_US.UTF-8 does not fix > it. I'm certain that openssh is 8-bit clean; a phenomenal number of things would break if this were not the case. Perhaps you simply don't have the en_US.UTF-8 locale generated on the remote machine, and the remote shell is running with a non-UTF-8 locale (setting the locale after you log in will not fix this)? If it's a Debian system, try 'dpkg-reconfigure locales' as root. -- Colin Watson [EMAIL PROTECTED]
