Answer the question
In order to leave comments, you need to log in
Debian encoding?
I understand that the question is hackneyed to holes, but I just can not understand what's the matter.
There is a server, everything was fine for the time being, I don’t even know what I did, but everything went wrong =)
I connect via putti with utf-8
ms encoding:
Then the problem is the following, editing the file in ms:
First thought, of course - the encoding is buggy exactly in ms, but vim:
And the most interesting cat:
Nano has the same properties. And before this was not, tell me who knows at least where to dig.
PS: locale reconfigured.
Answer the question
In order to leave comments, you need to log in
You need to specify the LANG=ru_RU.UTF-8 variable in putty (Connection->Data->Environment Variables)
Maybe the putty is crookedly assembled / the settings are completely lost if you try another version?
Check settings in Putty "Window->Translation" there are settings for character encoding.
+ when try to start mc with "-a" key -> "mc -a"
In the export LANG=ru_RU.UTF-8 console, there was the same problem. Helped me.
In the linux console
LANG=C
, restart mc and it will be displayed correctly. (If you have already played with putty configs, then try changing the encodings in the settings, windows, translate UTF8 or KOIR)
# Applied encodings
LANG=ru_RU.UTF-8
LANGUAGE=
LC_CTYPE="ru_RU. UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_PAPER ="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_ALL=
# Available encodings
[email protected]:~# locale -a
C
C.UTF
-8
en_GB
en_GB.iso88591
en_GB.iso885915
en_GB.utf8
POSIX
ru_RU
ru_RU.cp1251
ru_RU.iso88595
ru_RU.koi8r
ru_RU.utf8
russian
request) and select the default (second request) to choose better from the one in the ssh client (pytty for example)
[email protected]:~# dpkg-reconfigure locales
Generating locales (this might take a while)...
en_GB.ISO-8859 -1... done
en_GB.ISO-8859-15... done
en_GB.UTF-8... done
ru_RU.ISO-8859-5... done
ru_RU.CP1251... done
ru_RU.KOI8-R... done
ru_RU.UTF-8... done
Generation complete.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question