On Fri, Apr 10, 2020, at 3:29 AM, Daniele Pizzolli wrote:

Stephen J. Turnbull writes:

...

Daniele Pizzolli writes:

...

That's a waste of effort. Please add/merge it soon. Also any feedback will be appreciated.

Sorry about this. I think Abhilash (Cc'd) is the only person who knows about the process for adding translations, and is also doing the release engineering. He lives and works in the San Francisco Bay Area, which as you probably know has been a hot spot for COVID-19 infections. I doubt he has much spare time for Mailman at the moment. I know I don't.

Right now, we have a fairly automated way to do the translation for all our Mailman components. We use hosted Weblate (https://hosted.weblate.org/projects/gnu-mailman/) for all components including Core, Postorius, Django-mailman3 and Hyperkitty.

Weblate internally keeps the git repo in sync and any new translations are converted to git commits, one per author, per 24hrs. Then, Webalate is configured to send merge requests to Mailman's Gitlab repos, which can be merged like regular MRs. There are push events configured to notify Weblate to pull on each commit from Gitlab, so both repos are fairly in sync and we almost never have to deal with merge conflicts since after this setup. It is really convenient to do this.

Finally, during release, there is a script in the Mailman Core's root, generate-mo.sh, which basically compiles all the .po files to .mo files and requires GNU gettext. I did it for the first time in this release, but I am hoping to see if I can automate this so I don't forget, maybe hooking it up with setuptools somehow. Ideas & MRs are welcome, I am still not up to date with possibilities of Python packaging tools.

Rest of the projects are Django based and Django has commands to compile the translations at install time, so we don't do that yet at release time. I am again not up-to-date on what should be done here, so if I am doing it wrong, please let me know!

Thanks Stephen for the quick reply!

No worries, best wishes for everybody, safety first!

...

He has been more active on the mailing lists lately, so I hope there will be more release news soon. Please be patient.

Yes, sure, stay safe first, everything else has low priority!

...

Can you help me understand about why there is confusion about what's been done by whom? Are there multiple independent systems for doing the translations? Do you just do it differently because that's the way you work? I would think that we should have a system so that translators can log on and see if anything needs to be done for their language or if anybody has worked on it lately. Does the system lack that kind of work logging?

Let me try to explain. Yes, there are multiple independent path for sending the translations. The italian translation was empty.

You documentation says to send the po files here. That's what i did.

https://docs.mailman3.org/en/latest/translation.html#internationalization-i1...

Well, when I wrote the above docs, what I was really aiming for was something along the lines of, "Please use Weblate for translations always but if you didn't see this doc and already have a .po file lying around from perhaps earlier efforts, I'll take the .po file and do the manual work of merging it saving our translators from re-doing the same efforts on Weblate".

I don't know if the current language actually conveys that message, but if not, I'll gladly accept fixes to the docs.

I didn't know this until literally just right now, but Weblate does allow you to upload translations into the web interface1 from where it can just send us a Merge Request. I am going to update our documentation to reflect that instead of sending email here.

Daniele, Do you think you'll be able to do that? The process is fairly straight forward, but you'd have to do that for each component. I can do it on your behalf if you aren't able to, but I want the author information to reflect your name (which it won't if I upload to Weblate), so it would be nice that you get credits for your awesome work!

The weblate system does not pick up the translation made until somebody merge them into the source. So somebody unaware of my translations started the translation again.

Now, only 10/15 strings are translated using weblate, but it does not make any sense to do the work. I suggest to overwrite with my po that are complete and somewhat coherent and discard the ones from weblate. Contacting the other translator would be a nice action to do, at least to explain what happened. I will do it privately now, inviting him to join the list.

Before the overlap the step was simply to drop in my files, now maybe some merge step are required on weblate side. Hopefully weblate support something like overwrite/take the translation from PO.

Getting the translations from different path in the same time frame is very unlikely and having a conflict is quite remote in normal times. I guess that the restriction to mobility that almost everybody suffer now made it more likely...

Best, Daniele

-- thanks, Abhilash Raj (maxking)