[Mailman-Developers] Re: italian translations
On Mon, Apr 13, 2020, at 10:49 AM, Daniele Pizzolli wrote:
>
> Daniele Pizzolli writes:
>
> > Done, it seems that not everything (95% overall) was imported, but on my
> > side I have 100% (at least from 3 days ago).
> >
> > I will check it later why or tomorrow and report any issue!
>
> Hello!
>
> I do not know the details but the gnu gettext tools and weblate do
> something differently. Maybe there is a option to force the same
> behavior? To get the initial po for mailman I used the instruction in:
>
> src/mailman/docs/internationalization.rst
I just updated it yesterday to use update-pot.sh
>
> And translated everything. And now, after the import, I see additional
> lines like:
>
> msgid "list:admin:notice:subscribe.txt"
> msgstr ""
>
> I guess that those lines are related to the messages in
> src/mailman/templates/en/*txt.
Right.
>
> It seems that the weblate interface resolve in some way the reference
> and display the file content instead of the file name. Maybe there is
> something magic happening?
Yes, there is ;-)
So the issue I had was that these template files are .txt files and it is hard
to signal GNU xgettext to add them to the po files. So, I read a bit more about
translation guides and it turns out that msgid in .po files don't really have
to be the source string, but only an identifier and by default the identifier
is the english version.
So, I changed the identifier for only template files to be called the name of
the text file. This worked well for the code. They are called "monolingual" po
files and Weblate supports them. For helping translators, it will display
original source string from a reference .po file, which in our case is the
English version.
https://docs.weblate.org/en/latest/formats.html#bimono
This also remind me of a bug in update-pot.sh script, it doesn't add the right
source strings in the English .po file. I'll file a bug for it.
>
> I see that there are other languages templates... so what the
> translation should be? The translated string or the template file name
> containing the translation? Why not use the {% trans %} in templates?
Translation should be the translated string, but the msgid would be the file
name not the value. You can look at the English po file for reference.
> Ah, now I saw the update-pot.sh! But something is still not clear to
> me.
>
> Is there a way to get the file content as msgid or as comment to ease
> the offline translation? Or can I simply add my translation in place in
> src/mailman/templates/it/ and make a pull request?
You can look at the English translation as a reference, same as Weblate. But I
can also add the English text as comments in the po file if you feel that is
easier for you. It just needs updating the simple update-pot.sh script that you
saw already.
> Maybe just adding the template string to the po will streamline the
> interaction both with weblate and any offline tool while waiting for a
> long term solution. I may work on little patch if you agree.
>
> Let me know your suggestion and then I will complete the translations!
>
> Best,
> Daniele
>
--
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
[Mailman-Developers] Mailman 2.1.30 released
I am pleased to announce the release of Mailman 2.1.30 Python 2.6 is the minimum supported, but Python 2.7, preferably 2.7.17 - the final Python 2 release, is strongly recommended. This is a routine bug fix release with a few new features. See the attached README.txt for details. Mailman 2.1.30 will be the last release of the Mailman 2.1 branch from the GNU Mailman project. There has been some discussion as to what this means. It means there will be no more releases from the GNU Mailman project containing any new features. There may be future patch releases to address the following: - i18n updates. - security issues. - bugs affecting operation for which no satisfactory workaround exists. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.30 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan 2.1.30 (13-Apr-2020) New Features - Thanks to Jim Popovitch, there is now a dmarc_moderation_addresses list setting that can be used to apply dmarc_moderation_action to mail From: addresses listed or matching listed regexps. This can be used to modify mail to addresses that don't accept external mail From: themselves. - There is a new MAX_LISTNAME_LENGTH setting. The fix for LP: #1780874 obtains a list of the names of all the all the lists in the installation in order to determine the maximum length of a legitimate list name. It does this on every web access and on sites with a very large number of lists, this can have performance implications. See the description in Defaults.py for more information. - Thanks to Ralf Jung there is now the ability to add text based captchas (aka textchas) to the listinfo subscribe form. See the documentation for the new CAPTCHA setting in Defaults.py for how to enable this. Also note that if you have custom listinfo.html templates, you will have to add a tag to those templates to make this work. This feature can be used in combination with or instead of the Google reCAPTCHA feature added in 2.1.26. - Thanks to Ralf Hildebrandt the web admin Membership Management section now has a feature to sync the list's membership with a list of email addresses as with the bin/sync_members command. - There is a new drop_cc list attribute set from DEFAULT_DROP_CC. This controls the dropping of addresses from the Cc: header in delivered messages by the duplicate avoidance process. (LP: #1845751) - There is a new REFUSE_SECOND_PENDING mm_cfg.py setting that will cause a second request to subscribe to a list when there is already a pending confirmation for that user. This can be set to Yes to prevent mailbombing of a third party by repeatedly posting the subscribe form. (LP: #1859104) i18n - The Japanese translation has been updated by Yasuhito FUTATSUKI. - The German translation has been updated by Ludwig Reiter. - The Spanish translation has been updated by Omar Walid Llorente. - The Brazilian Portugese translation has been updated by Emerson de Mello. Bug Fixes and other patches - Fixed the confirm CGI to catch a rare TypeError on simultaneous confirmations of the same token. (LP: #1785854) - Scrubbed application/octet-stream MIME parts will now be given a .bin extension instead of .obj. - Added bounce recognition for a non-compliant opensmtpd DSN with Action: error. (LP: #1805137) - Corrected and augmented some security log messages. (LP: #1810098) - Implemented use of QRUNNER_SLEEP_TIME for bin/qrunner --runner=All. (LP: #1818205) - Leading/trailing spaces in provided email addresses for login to private archives and the user options page are now ignored. (LP: #1818872) - Fixed the spelling of the --no-restart option for mailmanctl. - Fixed an issue where certain combinations of charset and invalid characters in a list's description could produce a List-ID header without angle brackets. (LP: #1831321) - With the Postfix MTA and virtual domains, mappings for the site list -bounces and -request addresses in each virtual domain are now added to data/virtual-mailman (-owner was done in 2.1.24). (LP: #1831777) - The paths.py module now extends sys.path with the result of site.getsitepackages() if available. (LP: #1838866) - A bug causing a UnicodeDecodeError in preparing to
