[Pkg-mailman-hackers] Bug#668304: mailman: Translations should use unicode charset

[Santiago Vila]

On Tue, 10 Apr 2012, Ralf Jung wrote:

> Package: mailman
> Version: 1:2.1.13-5
> Severity: wishlist
> Tags: l10n
> 
> The mailman translations should use uncide as character set instead of the
> language-specific local character sets. I see no reason not to use unicode
> nowadays, and after some manual conversion as described on
> http://www.divideandconquer.se/2009/08/17/convert-mailman-translation-to-utf-8/
> mailman is working fine with unicode as charset for the German and English
> translation.

That solution is a hack, really. The gettext system was designed to
allow translators to use whatever charset encoding they wish, and
there is no need to change all the translations for that.

What you need is translations to be *shown* in your own charset, not
translations to *be* in UTF8, which is usually irrelevant.

The gettext system takes care of charset conversion but apparently
it's not working properly.

So yes, there seems to be a bug somewhere, but modifying all the
translations is the wrong solution.


(I was going to report this as a bug but I see that it's already reported)