Problem on Chinese input [6]

Problem on Chinese input

Wednesday, May 15, 2013 7:39 PM - Kelvin Yin

When I input Chinese, the screen only display "?" instead of the real word. My OS is Windows 8 Chinese Version.

The following two pictures demonstrate the situation.

Program Ver. : Xshell 4


Re: Problem on Chinese input

Wednesday, May 15, 2013 11:35 PM - Support

To display Chinese, try:

1. Change encoding to UTF-8 or a appropriate Chinese encoding from the Xshell toolbar

2. Change the font to Courier new or other Chinese font sets from the Xshell toolbar

---
Technical Support


Re: Problem on Chinese input

Monday, May 20, 2013 3:42 AM - Kelvin Yin

I have already modified the properties and font sets for sessions, but it does not work.
The problem is the session window can normally display Chinese words in files, but I cannot input Chinese.


Re: Problem on Chinese input

Monday, May 20, 2013 3:49 AM - Support

It looks like the IME (Chinese input system) is not the Windows default one. What is the name and version of the Chinese input system you are using?


---
Technical Support


Re: Problem on Chinese input

Monday, May 20, 2013 8:51 PM - Kelvin Yin

I uninstalled the Sogou input method(搜狗输入法6.6), but the problem was as the same as before.

My OS is Windows 8(Chinese Version), and even I use the Microsoft's Chinese input method, the problem still exists.

I reinstalled Xshell three times, it didn't work.

By the way, my colleages use the Xshell normally, the same Hardware and OS. It's really strange.


Problem is solved

Tuesday, May 21, 2013 5:24 PM - Kelvin Yin

I have formatted my hard disk E:, and the problem was solved. Now I can input Chinese in Xshell sessions.

Before, Windows 8 always notified there was a potential error in my hard disk E, it lasted for serveral days, so I formatted it.

That's it. I can use Xshell now.

Thanks!


Re: Problem on Chinese input

Tuesday, May 21, 2013 6:47 PM - Support

Thank you for letting us know. We were scratching our heads on this problem. Glad to hear the problem is now fixed.

---
Technical Support


Previous views: 151