Comment 3 for bug 341594

The character set in Mailman for German is iso-8859-1. I agree with you that everything should be unicode (real names are currently stored in Mailman as unicodes) and character sets should be those such as utf-8 that can faithfully represent unicodes, and I think Mailman is moving in this direction, and the newer translations are utf-8 encoded, but there are still many languages that use iso-8859-x or other (euc-jp, euc-kr, koi8-r) encodings. It is primarily the translators who maintain these translations who determine the character set.

>As I said: I was able to enter the name (of course, in Firefox), but submitting the changes did nothing, not even an error message. I do not understand your last sentence.

There does seem to be a bug in that I can enter (on a German Language list) Çeliko-lu and submit changes and what I entered displays as Çeliko-lu. I can enter -elikoǧlu and submit changes and what I entered displays as -elikoǧlu, but if I enter Çelikoǧlu and submit changes I get a "Bug in Mailman version 2.1.12". I can work on fixing that, but that doesn't explain why your Mailman doesn't report the error unless your hosting service has somehow modified Mailman to supress this display.

And what I meant by the last sentence is that the display that I see (-eliko&#487;lu) should really display the browser's rendering of the HTML entity rather that the raw entity (&#487;), but there is code in Mailman to prevent this being used as an XSS attack (say by putting <script ... as part of the real name) and that code changes &#487; into &amp;#487; so you see &#487; instead of the browser's rendering of character 487.