iso-8859-2 is inappropraite for Romanian - should be utf-8

[Mark Sapiro]

Mailman's use of iso-8859-2 encoding for Romanian is inappropriate. According to wikipedia, <http://en.wikipedia.org/wiki/ISO/IEC_8859-2>, iso8859-2 "can also be used for Romanian, but it is unsuitable for that language, because of lack of letters s and t with commas below, containing s and t with cedillas instead." Mailman's encoding should be changed to utf-8.

[baruch31 (jl-biasini)]

I can confirm that unless you consider all web interfaces as optional, unimportant feature, mailman is perfectly unusable in Romanian. The change to perform are trivial, when you know how to do it, but it took me one day to figure it out. Debugging the change is also difficult, because you have to go through all the page to be sure you didn't miss one. I, for instance, missed the encoding of the history page at first.

[Mark Sapiro (msapiro)]

If, by history page, you mean the encoding of the lists archives, then yes, you need to run 'bin/arch --wipe' after making the changes to recode the static list archive pages. You also need to recode any lists/LISTNAME/ro/*, templates/DOMAIN/ro/* and templates/site/ro/* templates you may have made. Otherwise, recoding the messages/ro/LC_MESSAGES/mailman.po message catalog and templates/ro/* templates along with changing the character set in th add_language() setting for 'ro' should be sufficient.

Did I miss anything?

[baruch31 (jl-biasini)]

you also have to change the header of some files, then don't all have it but some are mentionning iso8859-2 in their header

[Mark Sapiro (msapiro)]

I assume you are referring to these:

admlogin.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
archidxhead.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
archtoc.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
article.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
emptyarchive.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
listinfo.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
options.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
private.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
roster.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
subscribe.html:<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">

Thank you. I forgot those. Any others?

[baruch31 (jl-biasini)]

yes and of courses mailman.po
On 06/02/2015 21:41, Mark Sapiro wrote:
> I assume you are referring to these:
>
> admlogin.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> archidxhead.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> archtoc.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> article.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> emptyarchive.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> listinfo.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> options.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> private.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> roster.html: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
> subscribe.html:<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-2">
>
> Thank you. I forgot those. Any others?
>

[baruch31 (jl-biasini)]

That's it! And of course mailman.po

[Mark Sapiro (msapiro)]

Yes, I got all that, but I think in addition to all the things mentioned above, list admins may have to change various list attributes like 'description' that may be stored in iso-8859-2.