[Mailman-Developers] Re: italian translations
Hi Daniele, On Fr 10 Apr 2020 12:29:45 CEST, Daniele Pizzolli wrote: You documentation says to send the po files here. That's what i did. https://docs.mailman3.org/en/latest/translation.html#internationalization-i18n 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... Weblate is the primary translation location now for Mailman3. Working on .po files directly is / should be discouraged. What you can do to get the missing translations string / your translation strings into Mailman3 is logging into the hosted weblate site and transfer your translation work in to the Italian translation there. Then your work will be added to Mailman3 using the newly setup weblate integration workflow. Another, but more tricky option is one of the upstream devs (very likely Abhilash) to msgmerge your .po file into Weblate's latest version of the Italian translation file. But that demands time investments on Abhilash's side and IMHO this should be avoided. Greets, Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpUP0Mw_qOpi.pgp Description: Digitale PGP-Signatur ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: italian translations
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-i18n 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 interface[1] 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. [1]: https://docs.weblate.org/en/weblate-3.2.2/user/files.html#uploading-translations 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.
[Mailman-Developers] Re: Mailman Core 3.3.1rc1 release
On 4/10/20 3:31 AM, Abhilash Raj wrote: Hey Everyone, I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1rc1/ To install this release via pip, you can run: $ pip install --upgrade --pre mailman Note the `--pre` flag because this is a pre-release. If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. If there aren't any major breaking changes reported, the final release will be identical to this one. Well this is exciting and timely. I plan on upgrading Mailman core on my development server today to 3.3.1rc1 so we can start implementing the new REST API elements into Affinity. I will keep you posted via Gitlab if we run into any issues. Thanks! -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/ ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: italian translations
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. He has been more active on the mailing lists lately, so I hope there will be more release news soon. Please be patient. 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? Steve ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Mailman Core 3.3.1rc1 release
Hey Everyone, I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1rc1/ To install this release via pip, you can run: $ pip install --upgrade --pre mailman Note the `--pre` flag because this is a pre-release. If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. If there aren't any major breaking changes reported, the final release will be identical to this one. -- thanks, Abhilash Raj (maxking) ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
