Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am building a bilingual Japanese-English website and I am connecting to my own server (RedHat 8.0) with Putty. VSFTPd has no problem accepting and HTTPd has no problem serving files that have been encoded in Japanese (Shift_JIS and UTF-8). Internally, RH is treating these files just fine. But either at the command prompt locally or via Putty, I cannot enter Japanese characters directly (for instance with EMACS). Likewise, I cannot see the Japanese characters in files that have been previously sent via FTP. These files serve up just fine to a browser, they get garbled when rendered in Putty (by 'garbled' I mean they get rendered in, I think, the ASCII representation of Unicode, for example \200Ä).
From Putty's documentation, there is no problem using Asian (or other) character encodings. You simply choose the appropriate system in their 'translation' settings. I have installed Japanese as a language during set-up, (though I did not install KDE or Gnome as this was built simply to be a remote server) and I am confident that the server is capable of accepting Japanese input if I were running in a graphical shell.
I suspect I can change things in the /etc/sysconfig/i18n file, but I am not sure what to insert or change. At present, I have:
Turns out that PuTTY does not support Japanese character encodings out of the box regardless of what anyone says about how it works with any encoding you have installed on your machine. You need to modify the program to get it working in Nihongo. I was able to download a modified version of the code from a Japanese site and I am connecting to my box correctly and viewing and editing files as I need. I got the patch from http://www007.upp.so-net.ne.jp/bemax/arita/putty.html . In the event the site changes, the file containing the patch is called "putty056_jpini_patch.zip" and it modifies the program to access a language file called, "puttyjp.lng". Go google if you don't find what you are looking for. I expect the file name will change as PuTTY's version number changes, so be flexible.
The site mentioned above is in Japanese and any page linking to it will likely be in Japanese too. My Japanese is quite poor, but I was able to get thing going pretty easily. You can either apply the patch and recompile the program from PuTTY's source (download off the PuTTY site) or download the executable and language file directly. The version of this file is the same as a trojan-loaded one that was famously on Download.com for two weeks, so be warned. Furthermore...
**WARNING: PuTTY is a secure client from a trustworthy source. Even if the source of the code is honest and decent (which it may not be), patching the code may introduce weaknesses to the program that you would not like. Be cautious and use this only if you have no other option.**
That said, I am running the program as we speak and I haven't seen anything unusual. But I have my fingers crossed. And typing with fingers crossed is more difficult than you can imagine.
I sure hope you are still on, stutterbug. I'm struggling with the same problem, communicating with a Fedora Linux system running some Japanese programs. My only access to the machine is via SSH.
I found puttyjp.exe, and have started creating a puttyjp.lng file so that the interface is back to English. I've also tried several received data character sets, but none of those work.
What character set did/do you use?
What other settings do you need to make?
Are there any specific settings needed on the Linux side?
Any other suggestions would be greatly appreciated.
Yikes! That was five years ago. I've moved to Mac, whose BSD-style shell and built-in Japanese support solves all these ridiculous problems. I think that PuTTY's moved on and made it easier to integrate CJK, but I have no specific advice. There are a couple of pages on setting up PuTTY for Japanese: http://www.umiacs.umd.edu/~aelkiss/xml/displaywin.html, and http://anti.teamidiot.de/nei/2007/02...n_unicode_utf/ (this last one applies specifically to UTF-8, but you could apply it to any character encoding scheme, I think).
A quick google of "Putty 日本語" brings up some older pages that reference the present version of Putty (0.60) and an accompanying patch. For example, http://yebisuya.dip.jp/Software/PuTTY/. Might be worth trying. But like I said in my original answer, try to avoid patching PuTTY. It's job is to protect your security and patching it with code from an unknown source pretty much trashes that.
In addition, about all I can advise you is: 1) make sure you know which character set your server is using (if it's in Japan, it typically is EUC, ISO-2202-JP, or Shift-JIS on older systems and UTF-8 on newer ones) and stick to that for anything that touches the server including how you save files locally and how you connect to the server); 2) make sure Japanese input/output is supported natively in your OS (seeing how you posted hiragana in your reply, it looks like you do); and then 3) and try testing out a variety of character encoding schemes by saving some Japanese text in a variety of encodings on your Windows box and upload them to your server via FTP -- then try viewing them through PuTTY to see if they each display properly. This last step shouldn't be necessary but it may point out if the server has an issue with any specific encoding.
It's more recent than the one I'd found earlier. The puttyjp.lng file works -- just set the default language to English. The device I'm talking to uses "EUC-JP/AUTO DETECT JAPANESE". I'll have to see about working with EUC-JP encoded files under Windows.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.