Editing a file in CP866 encoding

[Michael Dukelsky]

Yury V. Zaytsev wrote:
> Unfortunately it is not as simple as this as (I guess) for the correct
> functioning of the remote access the sshd should be also aware of you
> using CP866 in your shell. At least, I was unable to read/write cyrillic
> after switching gnome-terminal to CP866 & executing LANG=ru_RU.cp866 on
> the server side as the screen was getting trashed by the control
> characters on non-ASCII input.

H-m-m. I did not find any possibility to set an encoding in either `man
5 sshd_config` or in `man 5 ssh_config`. But I disabled AcceptEnv in
/etc/ssh/sshd_config so that the client environment would not influence
on the server side. It did not help.

> Therefore, my guess is that you have to set ru_RU.cp866 globally
> in /etc/sysconfig/i18n and reboot, if you are not using local terminal.

[mike at fido ~]$ cat /etc/sysconfig/i18n
LANG="ru_RU.IBM866"
LC_NUMERIC=C
LC_MESSAGES=en_US.UTF-8
SUPPORTED="ru_RU.IBM866:ru_RU:ru"
SYSFONT="latarcyrheb-sun16"

[mike at fido ~]$ locale
LANG=ru_RU.IBM866
LC_CTYPE="ru_RU.IBM866"
LC_NUMERIC=C
LC_TIME="ru_RU.IBM866"
LC_COLLATE="ru_RU.IBM866"
LC_MONETARY="ru_RU.IBM866"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="ru_RU.IBM866"
LC_NAME="ru_RU.IBM866"
LC_ADDRESS="ru_RU.IBM866"
LC_TELEPHONE="ru_RU.IBM866"
LC_MEASUREMENT="ru_RU.IBM866"
LC_IDENTIFICATION="ru_RU.IBM866"
LC_ALL=

No effect.

> I know at least one person using a completely single byte non-ASCII
> setup which works for him, so if it is not the issue with your setup,
> you must be triggering some very cryptic and unreproducible bug.

At my box everything is reproduced 100%. Is it enough for the developers
to read this thread or should I post in some other list?

Best regards,
Michael Dukelsky