Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

On 01/16/2016 06:24 AM, Eva Isaksson wrote: > > To cut the long story short, the script worked without any problems. > Taking backups took more time than running the script and doing the > package upgrade. I'm glad the script worked for you. I have mentioned this issue to the Debian people who

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

I did the 2.1.18 upgrade this weekend, after some weighing of the options. In the long run, using the Debian package is less work intensive, so in the end my choice was the utf-8 conversion. > The script is at (mirrored > at

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

On 01/07/2016 01:20 PM, Mark Sapiro wrote: > > You can keep the Debian package with it's utf-8 character sets and > programmatically change all your lists so they work. In MM 2.1.19 I > changed the character sets for Russian and Romanian from koi8-r and > iso-8859-2 respectively to utf-8 because I

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

On 1/7/2016 2:40 PM, Eva Isaksson wrote: 2016-01-07 22:12 GMT+02:00 Mark Sapiro : On 01/07/2016 11:44 AM, Mark Sapiro wrote: I think simply re-entering the description and saving changes will fix this, but you should probably go through the entire web admin UI and do the same for any other non-

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

On 01/07/2016 12:40 PM, Eva Isaksson wrote: > 2016-01-07 22:12 GMT+02:00 Mark Sapiro >: > On 01/07/2016 11:44 AM, Mark Sapiro wrote: > >> I think simply re-entering the description and saving changes will fix >> this, but you should probably go through the entire web admi

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

2016-01-07 22:12 GMT+02:00 Mark Sapiro : On 01/07/2016 11:44 AM, Mark Sapiro wrote: > I think simply re-entering the description and saving changes will fix > this, but you should probably go through the entire web admin UI and do > the same for any other non-ascii strings. Am I right in thinking

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

On 01/07/2016 11:44 AM, Mark Sapiro wrote: > > You could install Mailman from source. See the FAQ at > for info. Just to be clear, by install from source I mean our source at e.g. , not some packager's source package. --

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

On 01/07/2016 04:40 AM, Eva Isaksson wrote: > > Also: > http://sources.debian.net/patches/patch/mailman/1:2.1.18-2/91_utf8.patch/ > > > If this means that debian is forcing everything to utf-8, what should I do, > if every package comes with this forced utf-8 encoding?

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

I tried to approach this problem by getting the source package from the debian repository. We are still running wheezy, so we need to stick to 2.1.18 for now. When I built the package, the resulting mailman.mo file for Finnish ends up utf-8 encoded (which I deduced by converting it back to a .po f

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

On 12/13/2015 09:18 AM, Eva Isaksson wrote: > > We have been running 2.15, on Debian, but because of the DMARC situation > it's time to upgrade to 2.18.. Why not 2.1.20? > Our upgrades have been rather routine so far, but this time we ran into > problems. Suddenly, the character encoding was p

[Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

Hi, I have a charset encoding problem that I'm unable to solve. I've been reading FAQs and list archives with little success. Our lists are in Finnish. The setup: our mailman installation uses its own translation file that is different from the Finnish translation that comes with the release. Bec