UTF-8 problem on my linode.
When I ssh a file from my machine with utf-8 into my linode it also appears that utf-8 chars get mangled (or maybe the ssh term can't display them, though it works with my other machines)
Any ideas ?
Thanks much.
12 Replies
did you generate the right locales on it?
(Latest 2.6 Stable (2.6.18.8-linode22))
I thought Debian 4 / etch was unicode by default, can you elaborate on generating the right locales ?
dpkg-reconfigure locales
The one difference i have on my linode is that the app server is proxied behind apache, but as far as i know apache is set to utf-8 as well.
Also I've compared response headers etc… and they all seem fine (utf-8)
Another diff is that my own machine uses tomcat and the server jetty, though they both suppose to support utf8 fine.
Will try to use the EXACT same app server and see.
@tcolar:
Same jetty version on both machine and still it works on my ubuntu 8.04 and not on the linode debian 4.0 –- weird !
Supposing you have properly configurated locales in your server, just check you have in /etc/ssh/sshd_config this
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
P.S. Why are you using old_stable (Debian 4.0) instead of current stable (Debian 5.0)?
What's the proper way to do that with a linode anyway, just do a standard debian dist-upgrade process ?
@tcolar:
No good reason other than I haven't upgarded.
What's the proper way to do that with a linode anyway, just do a standard debian dist-upgrade process ?
It's just a standard process provided that you've a standard installation.
Two suggestions (official Debian information):
Don't forget to update the kernel as well.
@BarkerJr:
Why would Linux settings have anything to do with this? This is between Java and your browser. If you're using the same version Java and app server, and the files were transfered as binary, you should get the exact same result.
Because tcolar asked two questions as a matter of fact and I'm replying to this problem:
@tcolar:
When I ssh a file from my machine with utf-8 into my linode it also appears that utf-8 chars get mangled (or maybe the ssh term can't display them, though it works with my other machines)