a.matveev@lan-project.ru writes:

https://translations.launchpad.net/mailman/3.0/+pots/mailman/ru/+details Is this is translation for use with mailman? Or what is it for?

That's for Mailman, but it's for version 3.0. I have no idea how useful it would be with Mailman 3 HEAD (soon to be released as Mailman 3.2). Probably the majority of messages are the same, so it should be pretty useful.

a.matveev@lan-project.ru writes:

Is there any documentation how to use this? I searched already, but without success.

This is managed entirely through Launchpad/Ubuntu. Nothing has been contributed back to upstream, and nobody has volunteered to do the work of pulling those files into our source tree and maintaining them as they are updated (there is a lot of churn in translations; keeping them in synch with release code is quite labor intensive).

I would assume you can drop the .po file(s) into mailman/src/mailman/messages/ru/LC_MESSAGE/ and the build and install process will do the right thing.

We would like to contribute further german translations, since there are still some parts missing, e.g. in the postorious interface. Would https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate be the right place to do so, so that everybody could use our translations?

If there are other areas in which you could use our help, please let us know.

Regards, Alex I wanted to set it up, but the requirement is to use a free hosted solution. (So transifex and crowdin are a no-go, they would be great to get translations, especially crowdin looks very active in that regard) I tried out zanata.org but it's extremely slow... The other option at the time was pootle (http://pootle.translatehouse.org), which doesn't offer hosting but some folks at gnu had a customized instance set up, but they discontinued the service.

I searched for a translation service for a private project and found weblate.org . They offer hosting (hosted.weblate.org) for open source projects and it looks like a couple of people are using it. You need to contact them if you want to set it up for an open-source project though and I didn't want to invest in it without knowing what the end-result would be...

Since I'm also mainly interested in German translations for my own installation, I opted to just use plain .po files and filed merge requests against the repositories. Postorius has translations (not perfect, but a start for the moderators that use my instance) included by now but my merge request for core is still outstanding https://gitlab.com/mailman/mailman/merge_requests/400/ Since I don't use Hyperkitty, I didn't translate that.

cheers, Simon

Thanks for the reply, Simon! We were thinking of using plain .po-files too, however, we couldn't find the matching "src" folder in our installation, do you have any more details where it or the .po-files may also be located? What component are you talking about? For Postorius and Hyperkitty you should be able to create the files needed according to this https://docs.djangoproject.com/en/2.0/topics/i18n/translation/#message-files First run "django-admin makemessages -l de" to create the .po files and after editing "django-admin compilemessages -l de" to compile them. You should be fine doing that in your production django-project. Otherwise you can clone the frontend projects and run the commands inside the project folders. (src/postorius or hyperkitty/). I know the second option works, since that's what I'm doing (I'm deploying from the git heads) but doing that in the production projects (where manage.py is located) should generate the same files. It might generate files for dependencies as well...

As for core, I only know how to translate the templates. I have no idea how the messages included in the source code should be translated.

On 07/03/2018 10:21 AM, Stephen J. Turnbull wrote:

Simon Hanna writes:

...

...

We would like to contribute further german translations, since there are still some parts missing, e.g. in the postorious interface. Would https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate be the right place to do so, so that everybody could use our translations?

I don't think that is the right place to do it, because I'm sure Ubuntu lags our releases by quite a bit. Obviously on Launchpad you should translate for their releases.

...

I wanted to set it up, but the requirement is to use a free hosted solution.

If by "free" you mean we can't afford to pay for a service, that's probably not true. If by "free" you mean the services you mention operate on non-free software, yes, RMS would indeed give us bat-guano about that, but it's not a 100% requirement. We did use Jira for some services for several years. So the main issue would be how long Abhilash is willing to put up with rms-guano. Yeah I meant the second definition :-) When I brought it up Barry said it had to be this way and that we don't want to self host it.

Daniel writes:

FYI: I did translate some strings a while ago. Have a look https://gitlab.com/dadosch/mailman3-german-translation-foo

The reason I didn't made a PR or similar was, that I didn't know where :D

I think you attach those messages in mailman/src/mailman/messages/de/LC_MESSAGES/de.po, and add a README.de at mailman/src/mailman/messages/de/README.de. The README contains information about how to participate in the German translation, such as who is the coordinator (or at least someone willing to read email about it and bring it to our attention), if you're using a translation management site, etc. Then submit the PR at http://gitlab.com/mailman/mailman.

If you are willing to coordinate the German translation, I bet Simon would be willing to cooperate in merging his translation. It would certainly be helpful in getting the process going to have an example of a translation effort for other languages to follow, and it looks like there's a lot of interest in German. So German may be a good place to start.

As I mentioned before, the core developers are not particularly focused on any translation effort. The policy issue about whether to centralize translation management and/or allow use of sites based on non-free software is delicate, as mentioned elsewhere, and there is the issue of coordinating the translation community with release management. Finally, there is the task of translation for Postorius and HyperKitty, which may benefit from a use of Django-specific tools (I'm not familiar with localizing Django applications so that may be completely stupid :-). So this is going to take time to plan.

Please feel free to lobby us, here and on mailman-developers. Contribution of effort (planning or coordination) is not necessary but of course would be welcome. Also, anybody who has participated in translation efforts who can describe a process that results in accurate translations while minimizing core developer and translator pain would be very welcome.

Steve