-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: Windows XP
Non ASCII chars get mangled when a new user is created.
Sample name: äöüß becomes äöüà (ok, this is extreme for usernames, but at
least full names must be enabled to have non ASCII characters).
It is one of the common problems when running an application server on Windows:
the default charset of the server is cp1252, the charset of the web application
is UTF-8. When you don't take care of this, you'll get in trouble.
There is a puzzling effect: After you edit the name as an administrator, the non
ASCII chars are correctly displayed!
Another effect is, that the user list becomes longer and longer whith entries like:
äöüÃ
äöüÃÂ
ÃÂäÃÂöÃÂüÃÂÃÂ
I couldn't reproduce this.
This is probably because you run Hudson on a servlet container that doesn't
handle encoding correctly. Starting 1.228, Hudson checks this and produeces a
warning (see the changelog for 1.228 for details), so if you are using an older
version, please check this.
Tomcat is perhaps the prime example of this. See
http://hudson.gotdns.com/wiki/display/JENKINS/Tomcat for more details about
Tomcat and encoding.
If your case doesn't apply to any of the above, please let us know your
container and Hudson version.