After centos5.2 is configured, Chinese characters can be displayed normally. After checking, the UTF-8 character set is supported.
The connection between putty and SSH Secure Shell found garbled characters, mainly including executing Vim garbled characters and su command garbled characters.
Run the $ locale command to view the result, as shown below:
Lang = zh_CN.UTF-8
Language = zh_cn: ZH
Lc_ctype = "zh_CN.UTF-8"
Lc_numeric = "zh_CN.UTF-8"
Lc_time = "zh_CN.UTF-8"
Lc_collate = "zh_CN.UTF-8"
Lc_monetary = "zh_CN.UTF-8"
Lc_messages = "zh_CN.UTF-8"
Lc_paper = "zh_CN.UTF-8"
Lc_name = "zh_CN.UTF-8"
Lc_address = "zh_CN.UTF-8"
Lc_telephone = "zh_CN.UTF-8"
Lc_measurement = "zh_CN.UTF-8"
Lc_identification = "zh_CN.UTF-8"
Lc_all =
Solution:
1. For putty0.6, download putty0.6
A. Modify/ECT/sysconfig/i18n on centos:
Lang = "zh_CN.UTF-8"
B. In the Configuration window of putty, modify windows-> appearance-> font setting to the new, and enter 10.
Modify the receive data assumed to be in which character set of translation:
UTF-8. (Because there is no Chinese Character Set in the down list, gb2312 or cp936 ).
After the modification is completed, Putty will normally support Chinese display.
2. For the SSH Secure Shell version.
A. Change the font to, but it is garbled,
B. Modify/ECT/sysconfig/i18n of centos:
Lang = "zh_cn.gb18030"
Language = "zh_cn.gb18030: zh_cn.gb2312: zh_cn"
Supported = "zh_cn.gb18030: zh_cn: Zh: en_US.UTF-8: en_us: en"
Sysfont = "latarcyrheb-sun16"
--- The above content was found on the internet and written according to it.
The SSH Secure Shell connection is found to display Chinese characters normally.
Use $ locale to check whether the configuration above is changed to gb18030 encoding.
** However, Putty is used for connection, but it turns into garbled characters. I understand that putty still uses utf8 encoding,
When configuring SSH Secure Shell, centos is changed to gb18030 encoding, so garbled.
C. Go to the server, restart centos, and find that Chinese characters are displayed normally.
3. If you find that there is a problem with SSH Secure Shell or related problems, reconfigure putty,
For the configuration scheme, refer to the above configuration.
Conclusion:
Because the SSH Secure Shell window conforms to the window display, it is temporarily set to use the SSH Secure Shell client.
It is also bound with the FTP upload function, which is relatively convenient.
Change: consider setting up MySQL and other places to use UTF-8 encoding. All users still use the putty client, and the system encoding is changed to UTF-8.
