PuTTY: inputting some special characters doesn't work (Romanian)

0

I use PuTTY to connect to a CentOS server, and I sometimes need to enter Romanian characters from the keyboard. I use Windows 7 on the client computer; I have the server locale set up as en_US.UTF-8, and PuTTY is also configured for UTF-8.

I do NOT have any issues entering characters "î" and "ă" from the keyboard, and I also wouldn't have any problems entering the legacy cedilla characters "ş" (U+015F) and "ţ" (U+0163).

However, I can't enter the proper (comma) counterparts of the cedilla legacy characters "ș" (U+0219) and "ț" (U+021B). Whenever I try to use these two from the keyboard I get a question mark in the console. The issue is not related to the font I'm using in PuTTY, because I can copy/paste them (e.g. from this post), and I can generate them on the Linux host, e.g. by using

$ perl -Mcharnames=:full -CS -wle 'print "\N{LATIN SMALL LETTER S WITH COMMA BELOW}"'

I use Microsoft's stock keyboard settings for Romanian -- both "Romanian (Standard)" and "Romanian (Programmers)" produce the same results; "Romanian (Legacy)" works properly, but produces the legacy cedilla variants, which I'd rather not use.

How do I fix this?

Bogdan Stăncescu

Posted 2013-01-03T13:00:56.033

Reputation: 111

1Are you perhaps using screen? If so you also need to configure screen to use UTF-8 – None – 2013-01-03T13:03:58.330

Nope, just plain stock bash. – None – 2013-01-03T13:16:59.400

In my environment LANG=en_US.UTF-8 not LOCALE, but I don't know if that makes a difference for you. – mhitza – 2013-01-03T14:46:27.620

Yep, same here, I just didn't want to list all output from locale. – None – 2013-01-03T15:13:27.167

Answers

1

After a long history* this bug has been fixed in release 0.63 http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist//win-tounicodeex.html


Costin Gușă

Posted 2013-01-03T13:00:56.033

Reputation: 637

Oh, if it's a bug in putty then it's a bug in putty, and that's that. I thought I was doing something wrong (I thought I just had to fiddle with some locale settings somewhere). – Bogdan Stăncescu – 2013-07-13T13:18:38.533