I work extensively on a Windows desktop. However, I do SSH into Linux servers often and I do so using PuTTY, a free and open source client. Everything works peachy. However, I recently had occasion to work extensively with some Unicode source data and I found that there were times when I thought that there were encoding issues with the data as they were not being displayed correctly on my screen. It turns out that there was really nothing wrong with the data and that it was PuTTY was misinterpreting the data to be in the wrong encoding.
Fixing this is something of a cinch:
- In the PuTTY configuration window, load the saved session that you use to connect to the server.
- In the Category options tree on the left, choose Translation within the Windows branch.
- Within, set the option Received data assumed to be in which character set to UTF-8 (in my case).
- Go back to the Session category and click on the Save button to save our changes to the currently loaded session.
- To do this within a live session, right click on the PuTTY title bar and choose Change settings which should allow you to do the same.
This problem also affects other Windows terminals including
cmd.exe. From what I've read, the fix for
cmd.exe is to use the
chcp command to change the active code page. Type
chcp /? for more information.
Hope this helps!
- Log in to post comments