I contributed in january to translate to spanish all the items left in Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I thought they will be used in the next upgrade, but I cannot see any improvement and there are many words untranslated.
Is there any way to upgrade the .po files in order to get the last translation?
P.S.: I will follow translating the Weblate updates, by the way.
On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I contributed in january to translate to spanish all the items left in Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I thought they will be used in the next upgrade, but I cannot see any improvement and there are many words untranslated.
The Spanish translations for Mailman core and HyperKitty are currently completely up to date with weblate. django-mailman3 differs in one string that was translated on Feb 10 and hasn't yet been merged. Postorius also differs in a few places from the Feb 10 version that hasn't yet been merged.
Other than that, the translations should be good.
Is there any way to upgrade the .po files in order to get the last translation?
For the web UI you need to run the django management compilemessages
command. For Mailman core you need to run
cd mailman/messages/es/LC_MESSAGES
msgfmt -o mailman.mo mailman.po
to compile the mailman.po file for gettext.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/2/21 20:15, Mark Sapiro wrote:
On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I contributed in january to translate to spanish all the items left in Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I thought they will be used in the next upgrade, but I cannot see any improvement and there are many words untranslated.
The Spanish translations for Mailman core and HyperKitty are currently completely up to date with weblate. django-mailman3 differs in one string that was translated on Feb 10 and hasn't yet been merged. Postorius also differs in a few places from the Feb 10 version that hasn't yet been merged.
Ok. Thanks for checking it. I put my little contribution in Weblate and I like that it could be used by anyone.
Other than that, the translations should be good.
Is there any way to upgrade the .po files in order to get the last translation?
For the web UI you need to run the django management
compilemessagescommand.
I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error:
su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified.
if I try with --settings param (for I missunderstood the error message) it shows the same:
su -m mailman3 -c "python3 manage.py compilemessages --settings settings" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified.
I tried to find any doc regarding the use of the "compilemessages" command but I couldn't
As far as I can see (I runned it with -h parm) this had to be related to the main python module, but I cannot understand why the pip upgrade did not do the job.
I'm lost.
Can you, please, point me in the right direction?
For Mailman core you need to run
cd mailman/messages/es/LC_MESSAGES msgfmt -o mailman.mo mailman.poto compile the mailman.po file for gettext.
On Fri, 2021-02-12 at 09:04 +0100, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 11/2/21 20:15, Mark Sapiro wrote:
On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I contributed in january to translate to spanish all the items left in Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I thought they will be used in the next upgrade, but I cannot see any improvement and there are many words untranslated.
The Spanish translations for Mailman core and HyperKitty are currently completely up to date with weblate. django-mailman3 differs in one string that was translated on Feb 10 and hasn't yet been merged. Postorius also differs in a few places from the Feb 10 version that hasn't yet been merged.
Ok. Thanks for checking it. I put my little contribution in Weblate and I like that it could be used by anyone.
Actually, I was going to ask these same questions, because I dedicated some hours to get the Spanish translation nearly finished, it was kind of a "spiritual" need for me, being the person that seeded the efforts for Mailman i18n support back in the late '90s :-) :-)
I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error:
su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified.
I got this very same error, and was also confused, as manage.py runs at the project level, not application level.
I'm lost.
Do not feel bad, Guillermo, an old time pythonist with message translations experience, that uses i18n for some of his applications, is also dazzled and confused :-)
Confused-with-translations-ly, Victoriano.
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
On 2/12/21 12:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 11/2/21 20:15, Mark Sapiro wrote:
For the web UI you need to run the django management
compilemessagescommand.I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error:
su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified.
The documentation is at, e.g., https://docs.djangoproject.com/en/3.1/ref/django-admin/.
If the manage.py in the directory in which you ran this is the correct one for your Mailman Django project, I don't know why it didn't work.
Is your Mailman installed in a virtualenv? If so, was the virtualenv activated?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 12/2/21 21:24, Mark Sapiro wrote:
On 2/12/21 12:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 11/2/21 20:15, Mark Sapiro wrote:
For the web UI you need to run the django management
compilemessagescommand. I tried to run this using the same command as I did for the "collectstatic" (that solved all my previous problems for the upgrade) and "migrate" runs but it shows me an error:su -m mailman3 -c "python3 manage.py compilemessages" CommandError: This script should be run from the Django Git checkout or your project or app tree, or with the settings module specified.
The documentation is at, e.g., https://docs.djangoproject.com/en/3.1/ref/django-admin/. Didn't find it. Thanks If the manage.py in the directory in which you ran this is the correct one for your Mailman Django project, Yes, it is. I don't know why it didn't work. :(
Is your Mailman installed in a virtualenv?
No. It's system's wide.
Thanks for your answer.
If so, was the virtualenv activated?
On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote:
If the manage.py in the directory in which you ran this is the correct one for your Mailman Django project, I don't know why it didn't work.
Me neither :-( That's why I asked, and probably Guillermo, as well.
Is your Mailman installed in a virtualenv? If so, was the virtualenv activated?
No virtualenv. Mine is deployed using system python on a CentOS 7 system, toghether with another in house developed low requirements Django project, both served by uWSGI vassals.
And then, all of a sudden, while I was writting this, it dawned on me!
Postorius, Hyperkitty and django-mailman are installed with pip, so, the end up in the site-packages directory (usually /usr/local/lib/python3.x/site-packages), but, normally, django projects are deployed somewhere in the web server hierarchy (/var/ww/django in my case, due to old personal tastes), and applications properly defined in the settings.py for the project.
So, the message files are out of reach for manage.py.
Changing to /usr/local/lib/python3.x/site-packages/X (with X being postorius, hyperkitty and django_mailman3) and using django-admin compilemessages all works!
Thanks for pushing my thoughts in the right direction!
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
On 13/2/21 11:55, Victoriano Giralt wrote:
On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote:
If the manage.py in the directory in which you ran this is the correct one for your Mailman Django project, I don't know why it didn't work. Me neither :-( That's why I asked, and probably Guillermo, as well.
Is your Mailman installed in a virtualenv? If so, was the virtualenv activated? No virtualenv. Mine is deployed using system python on a CentOS 7 system, toghether with another in house developed low requirements Django project, both served by uWSGI vassals.
And mine, as well, in a FreeBSD 12.2-RELEASE, no virtualenv and uWSGI approach with apache24 server.
And then, all of a sudden, while I was writting this, it dawned on me!
Postorius, Hyperkitty and django-mailman are installed with pip, so, the end up in the site-packages directory (usually /usr/local/lib/python3.x/site-packages),
That is my case, too.
but, normally, django projects are deployed somewhere in the web server hierarchy (/var/ww/django in my case, due to old personal tastes), and applications properly defined in the settings.py for the project.
So, the message files are out of reach for manage.py.
Changing to /usr/local/lib/python3.x/site-packages/X (with X being postorius, hyperkitty and django_mailman3) and using django-admin compilemessages all works!
And for me as well. Thanks a lot Victoriano, I owe you a beer
Thanks for pushing my thoughts in the right direction!
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
El sáb, 13-02-2021 a las 12:10 +0100, Guillermo Hernandez (Oldno7) via Mailman-users escribió:
And for me as well. Thanks a lot Victoriano, I owe you a beer
If you are based in Spain, maybe we can take care of that when we are allowed to move around the country :-)
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
On 13/2/21 12:13, Victoriano Giralt wrote:
El sáb, 13-02-2021 a las 12:10 +0100, Guillermo Hernandez (Oldno7) via Mailman-users escribió:
And for me as well. Thanks a lot Victoriano, I owe you a beer If you are based in Spain, maybe we can take care of that when we are allowed to move around the country :-)
That was why I mentioned it :) Not because all of the people working in Mailman 3 do not deserve a beer from me, but because we are in the same country. I'm from Alicante (Alfaz del Pi, next to Benidorm).
As you said, when we beat down the pandemia.
On Thu, 2021-02-11 at 11:15 -0800, Mark Sapiro wrote:
For Mailman core you need to run
cd mailman/messages/es/LC_MESSAGES msgfmt -o mailman.mo mailman.poto compile the mailman.po file for gettext.
Mark, I'd say the Mailman core message files taht get installed by pip are "a bit outdated" (source files dates point to a nightly build) ... proof here:
[root@isoc-es messages]# pwd /usr/local/lib/python3.6/site-packages/mailman/messages [root@isoc-es messages]# ll */LC*/ ca/LC_MESSAGES/: total 164 -rw-r--r-- 1 root root 66479 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 95099 Oct 30 17:30 mailman.po
de/LC_MESSAGES/: total 184 -rw-r--r-- 1 root root 81693 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 104049 Jan 17 20:41 mailman.po
en/LC_MESSAGES/: total 172 -rw-r--r-- 1 root root 74350 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 97233 Oct 30 17:30 mailman.po
eo/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 321 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55254 Oct 30 17:30 mailman.po
es/LC_MESSAGES/: total 184 -rw-r--r-- 1 root root 80741 Feb 12 09:18 mailman.mo -rw-r--r-- 1 root root 102963 Nov 7 01:50 mailman.po
fr/LC_MESSAGES/: total 124 -rw-r--r-- 1 root root 42261 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 81452 Jan 17 20:41 mailman.po
he/LC_MESSAGES/: total 180 -rw-r--r-- 1 root root 79940 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 101264 Jan 17 19:20 mailman.po
hu/LC_MESSAGES/: total 72 -rw-r--r-- 1 root root 9500 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 59290 Feb 3 02:44 mailman.po
it/LC_MESSAGES/: total 180 -rw-r--r-- 1 root root 78543 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 100864 Jan 17 20:41 mailman.po
ja/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1296 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55755 Oct 30 17:30 mailman.po
ko/LC_MESSAGES/: total 164 -rw-r--r-- 1 root root 66668 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 94598 Oct 30 17:30 mailman.po
nb_NO/LC_MESSAGES/: total 68 -rw-r--r-- 1 root root 6263 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 57744 Jan 17 19:20 mailman.po
pl/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1933 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 56068 Oct 30 17:30 mailman.po
pt/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1734 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55963 Oct 30 17:30 mailman.po
ru/LC_MESSAGES/: total 80 -rw-r--r-- 1 root root 12651 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 62127 Oct 30 17:30 mailman.po
sq/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 321 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55227 Oct 30 17:30 mailman.po
tr/LC_MESSAGES/: total 168 -rw-r--r-- 1 root root 73537 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 96452 Jan 17 20:41 mailman.po
zh_Hans/LC_MESSAGES/: total 64 -rw-r--r-- 1 root root 4945 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 57269 Jan 17 19:20 mailman.po
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
Victoriano Giralt writes:
Mark, I'd say the Mailman core message files taht get installed by pip are "a bit outdated" (source files dates point to a nightly build) ... proof here:
I don't understand what you think this proves. We can't do the translations ourselves; we don't have the lingistic skills. So the dates on the .po files are going to reflect translator activity as well as core dev activity. Am I missing something that we can do something about?
On Fri, 2021-02-12 at 19:53 +0900, Stephen J. Turnbull wrote:
Victoriano Giralt writes:
Mark, I'd say the Mailman core message files taht get installed by pip are "a bit outdated" (source files dates point to a nightly build) ... proof here:
I don't understand what you think this proves. We can't do the translations ourselves; we don't have the lingistic skills. So the dates on the .po files are going to reflect translator activity as well as core dev activity. Am I missing something that we can do something about?
Thanks Stephen for reminding me that sometimes I write what looks like proper English on the surface, but the meaning of it comes from the deep corners of my mind in some long forgotten dialect :-)
I just wanted to make visible that the .mo files were a "bit old". For example, Guillermo, in this thread, pointed that the Spanish translation was quite compelte. Actualy, I spent some hours bringing them to 100% around Christmas. But, the .mo file for es from the pip install --update i did recently is dated November 7th. I have definitely added a lot of translated material from then until the end of the year.
I know the translation happens outside the development community. I tried to point that there might be some synchronisation problem, so to say, between the translation site and the packaging of the latest mailman release.
I hope this time I've managed to express myself better ;-) I swear my brain was thinking in English as a wrote :-) :-)
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
On 2/12/21 3:21 AM, Victoriano Giralt wrote:
I just wanted to make visible that the .mo files were a "bit old". For example, Guillermo, in this thread, pointed that the Spanish translation was quite compelte. Actualy, I spent some hours bringing them to 100% around Christmas. But, the .mo file for es from the pip install --update i did recently is dated November 7th. I have definitely added a lot of translated material from then until the end of the year.
Why do you say the .mo files are old. The timestamps are all Feb 3 02:47 which is when the package was built for PyPI.
I know the translation happens outside the development community. I tried to point that there might be some synchronisation problem, so to say, between the translation site and the packaging of the latest mailman release.
When things are changed on weblate, we get automatically generated merge requests to update our source. We don't always merge them immediately, but we certainly do merge all the outstanding ones before making a release.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, 2021-02-12 at 12:36 -0800, Mark Sapiro wrote:
Why do you say the .mo files are old. The timestamps are all Feb 3 02:47 which is when the package was built for PyPI.
Because my brain goes faster than my fingers and I say the reverse of what I mean.
I meant .mo files, all .po where properly dated, and I reversed the meaning of my thoughs while typing.
Thanks for brining my confussion to my (and everybody's) attention, and my appologies for the noise.
When things are changed on weblate, we get automatically generated merge requests to update our source. We don't always merge them immediately, but we certainly do merge all the outstanding ones before making a release.
I'm 95% certain that I edited messages after Nov 7th in the Spanish translation of both mailman, postorius and hyperkitty, but the .po file is dated Nov 7h. Actually, I did a review of outstanding strings when Abhilash annonced the RC for the current version. That is why I was bit surprised. But then, it may be me and my faint memory.
And, of course, I'm very grateful and happy with all the work that is being done on Mailman3.
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
Victoriano Giralt writes:
Thanks Stephen for reminding me that sometimes I write what looks like proper English on the surface, but the meaning of it comes from the deep corners of my mind in some long forgotten dialect :-)
Your English is fine, it was just my lack of imagination: on February 12, I couldn't conceive of February 3 being even a little "old"!
More important, as long as the .mo file is more recent than the .po file, that's the best the release manager can do. I haven't been involved in the release process, so I can't swear to it personally, but if Mark says that new translations generate a merge request automatically, and we make sure that the translations are merged before release, I believe him. That's optimal as far I am concerned.
Perhaps some enterprising soul would be willing to automate production of pip'able packages containing only new translations, but without that, I don't see how to beat our current procedures. (I wouldn't want to use such a thing, though, I'd be too afraid that one day all the translations would be replaced with Dril tweets!)
On 13/2/21 9:04, Stephen J. Turnbull wrote:
Victoriano Giralt writes:
Thanks Stephen for reminding me that sometimes I write what looks like proper English on the surface, but the meaning of it comes from the deep corners of my mind in some long forgotten dialect :-)
Your English is fine, it was just my lack of imagination: on February 12, I couldn't conceive of February 3 being even a little "old"!
But... here is a thing that I can not understand: If the source (the .po file) is from november 7th, it doesn't matter how many times you recompile it: the result will be the same.
I did what Mark recommended.
Before that:
/usr/local/lib/python3.7/site-packages/mailman/messages/es/LC_MESSAGES # ls -la total 192 drwxr-xr-x 2 root wheel 512 Feb 8 12:00 . drwxr-xr-x 3 root wheel 512 Feb 8 12:00 .. -rw-r--r-- 1 root wheel 80700 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root wheel 102963 Nov 7 01:50 mailman.po
Then...
/usr/local/lib/python3.7/site-packages/mailman/messages/es/LC_MESSAGES # msgfmt -o mailman.mo mailman.po
And that is: the same .mo file just with different date
/usr/local/lib/python3.7/site-packages/mailman/messages/es/LC_MESSAGES # ls -la total 192 drwxr-xr-x 2 root wheel 512 Feb 13 11:09 . drwxr-xr-x 3 root wheel 512 Feb 13 11:09 .. -rw-r--r-- 1 root wheel 80700 Feb 13 11:09 mailman.mo -rw-r--r-- 1 root wheel 102963 Nov 7 01:50 mailman.po
I'm not trying to diminish the effort and the excelent work that are indeed making all of you. I appreciate that so much. But is evident to me that something fails in the translation path chain of upgrades. If you access the postorius web to manage subscriptions you can see a full mixed language words. It's not a life or death item... but it has not to be that way as the terms, as far as I know, are 100% translated (at least in spanish). And the subscriptors complain.
If that is not a thing that the release manager can do, well... We are stucked, isn't it?
I don think it has to be a matter of "automate production of pip'able packages containing only new translations": a new version has just released and the localization languages, at least spanish, were not merged into it for the last Weblate updates.
I will wait untill the next update, this thread is closed to me.
Thanks, again, for all your good work.
More important, as long as the .mo file is more recent than the .po file, that's the best the release manager can do. I haven't been involved in the release process, so I can't swear to it personally, but if Mark says that new translations generate a merge request automatically, and we make sure that the translations are merged before release, I believe him. That's optimal as far I am concerned.
Perhaps some enterprising soul would be willing to automate production of pip'able packages containing only new translations, but without that, I don't see how to beat our current procedures. (I wouldn't want to use such a thing, though, I'd be too afraid that one day all the translations would be replaced with Dril tweets!)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
But... here is a thing that I can not understand: If the source (the .po file) is from november 7th, it doesn't matter how many times you recompile it: the result will be the same.
Correct, but the point is if you download the latest gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file in the distribution, you will find they are identical, so it it appears that the weblate translation hasn't changed since that time.
If there are issues in this mailman.po, they exist in weblate too and need to be fixed there.
Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> and submit a merge request to add them to a mailman/templates/es/ directory.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 13/2/21 20:00, Mark Sapiro wrote:
But... here is a thing that I can not understand: If the source (the .po file) is from november 7th, it doesn't matter how many times you recompile it: the result will be the same. Correct, but the point is if you download the latest gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file in the distribution, you will find they are identical, so it it appears
On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: that the weblate translation hasn't changed since that time.
If there are issues in this mailman.po, they exist in weblate too and need to be fixed there.
That clarifies all. Thanks. As I said in my previous message, I'll wait for the next upgrade and hopingly the translations done after 7h of november (by others and me) will be there.
Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> and submit a merge request to add them to a mailman/templates/es/ directory.
I will make the template translations locally, test them, and then, if they are yet lacking in the main repo, follow your suggestion.
Thanks.
On 2/13/21 11:52 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 13/2/21 20:00, Mark Sapiro wrote:
If there are issues in this mailman.po, they exist in weblate too and need to be fixed there.
That clarifies all. Thanks. As I said in my previous message, I'll wait for the next upgrade and hopingly the translations done after 7h of november (by others and me) will be there.
What translations are those? Please give specific examples. What I am saying is Mailman core 3.3.3 is currently up to date with weblate. There are no Spanish translations for core done after 7 November in weblate and weblate shows 100% completion for Spanish for Mailman core.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió:
What translations are those? Please give specific examples. What I am saying is Mailman core 3.3.3 is currently up to date with weblate. There are no Spanish translations for core done after 7 November in weblate and weblate shows 100% completion for Spanish for Mailman core.
Mark, please, how do you check when translations happened? Nov 7th is a very significant date for me (it is my wedding anniversary) and I'm 90% sure that I dedicated time to Weblate after that date...
All strings related to Mailman (core, django_mailman3, postorius and hyperkitty) are translated into Spanish 100%, but the interfaces, after updating to the latest releases, are still in Englanish (more English than Spanish).
This is not a fight, we want to help, but do not know how.
Thanks!
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
On 2/13/21 4:08 PM, Victoriano Giralt wrote:
Mark, please, how do you check when translations happened? Nov 7th is a very significant date for me (it is my wedding anniversary) and I'm 90% sure that I dedicated time to Weblate after that date...
With respect to Mailman core, all I'm doing is downloading the .po for Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po from the Mailman core 3.3.3 package on PyPI and they are identical.
If there are translated strings on weblate that are different from that, they don't show up in the downloaded <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>.
All strings related to Mailman (core, django_mailman3, postorius and hyperkitty) are translated into Spanish 100%, but the interfaces, after updating to the latest releases, are still in Englanish (more English than Spanish).
This is not a fight, we want to help, but do not know how.
And I too want to help. It would be a help to me if you can give me examples of specific strings whose weblate translation differs from what's in the distributed .po files.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
El sáb, 13-02-2021 a las 16:44 -0800, Mark Sapiro escribió:
On 2/13/21 4:08 PM, Victoriano Giralt wrote:
Mark, please, how do you check when translations happened? Nov 7th is a very significant date for me (it is my wedding anniversary) and I'm 90% sure that I dedicated time to Weblate after that date...
With respect to Mailman core, all I'm doing is downloading the .po for Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po from the Mailman core 3.3.3 package on PyPI and they are identical.
If there are translated strings on weblate that are different from that, they don't show up in the downloaded <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>;.
And you are very right and I have fallen as a newbee ... and first of all I apologise for the noise.
I've been doing diffs with files downloaded from Weblate and those installed on the server by pip. As I should have done from the start.
Mailman core and hyperkitty show no differences. Postorius shows a bunch and django_mailman3 just a couple.
I leave for others a more detailed check of the strings between downloaded .po files and Weblate online strings, it's too late here.
And I too want to help. It would be a help to me if you can give me examples of specific strings whose weblate translation differs from what's in the distributed .po files.
And you have helped me, making me thing twice and stop moaning and going for the facts.
Apologetic-thankful-big-mouth-shut-ly, Victoriano.
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
On 13/2/21 23:53, Mark Sapiro wrote:
On 2/13/21 11:52 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 13/2/21 20:00, Mark Sapiro wrote:
If there are issues in this mailman.po, they exist in weblate too and need to be fixed there. That clarifies all. Thanks. As I said in my previous message, I'll wait for the next upgrade and hopingly the translations done after 7h of november (by others and me) will be there.
What translations are those? Please give specific examples. What I am saying is Mailman core 3.3.3 is currently up to date with weblate. There are no Spanish translations for core done after 7 November in weblate and weblate shows 100% completion for Spanish for Mailman core.
Well.. It surely is in the case of mailman core, but not in postorius, hyperkitty and django_mailman3. And these are what are serving the translated terms what the users see.
I did some exploration this morning (Spain time) in the weblate statistics and archives and I found that the changes done from Victoriano and me were recorded. I did a screencopy of all that if someone has any doubt about it. I downloaded this files:
-rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po
The thing is that they differ from the .po installed via pip upgrade. Mostly, as said, postorius, hyperkitty and django_mailman3.
I saved a backup copy of the "django.po" that lies in the packages path for the es language. In my case
/usr/local/lib/python3.7/site-packages/[package]/locale/es/LC_MESSAGES
and replaced by the downladed file, changing the name (as all of them was named django.po in destination).
Then I did, as you pointed in a message and Victoriano found the right way in our systems, a django-admin compilemessages for each package.
And now I have all the postiorius web interface correctly translated (at least almost all of it). Now I can make a tutorial for my moderators and users without them complaining about the mixing language terms.
I have also a screencopy of before-after If someone wants to see the changes.
Thanks all for your support.
On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I did some exploration this morning (Spain time) in the weblate statistics and archives and I found that the changes done from Victoriano and me were recorded. I did a screencopy of all that if someone has any doubt about it. I downloaded this files:
-rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po
The thing is that they differ from the .po installed via pip upgrade. Mostly, as said, postorius, hyperkitty and django_mailman3.
The latest packages in PyPI (pip) were released on Feb 2 except for django-mailman3 which was released on Jan 15. They don't include updates after those dates.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 14/2/21 18:42, Mark Sapiro wrote:
On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I did some exploration this morning (Spain time) in the weblate statistics and archives and I found that the changes done from Victoriano and me were recorded. I did a screencopy of all that if someone has any doubt about it. I downloaded this files:
-rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po
The thing is that they differ from the .po installed via pip upgrade. Mostly, as said, postorius, hyperkitty and django_mailman3.
The latest packages in PyPI (pip) were released on Feb 2 except for django-mailman3 which was released on Jan 15. They don't include updates after those dates.
And I say that I (and others ) have made translations in postorius, hyperkitty an Django_mailman3 in January. Yes, I've made some changes in february 10th, but It were a pair of messages.
But that's all about this from me. If in the next upgrade I find that there is any translation missing, I know, thanks to you and Victoriano, how to handle it. And if some new admin installs mailman 3 and try to localize it to spanish and comes to this list to ask how to do a more complete translation... well, these messages can point him or her to the right direction.
My postorius web access to the lists is now almost completely translated to spanish and now I can help the users without hesitating language problems.
Thanks. Thanks a lot.
El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) via Mailman-users escribió:
On 13/2/21 20:00, Mark Sapiro wrote:
But... here is a thing that I can not understand: If the source (the .po file) is from november 7th, it doesn't matter how many times you recompile it: the result will be the same. Correct, but the point is if you download the latest gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file in the distribution, you will find they are identical, so it it appears
On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: that the weblate translation hasn't changed since that time.
If there are issues in this mailman.po, they exist in weblate too and need to be fixed there.
That clarifies all. Thanks. As I said in my previous message, I'll wait for the next upgrade and hopingly the translations done after 7h of november (by others and me) will be there.
I've visited Weblate, all Spanish strings are translated. Spanish is 100% translated, but, none of them have been "approved", whatever that is. It seems that a reviewer needs to approve the translation in order for them to be incorporated or released or whatever. I was sure I had reviewed everything between November 7th and the day Abhilash announced the release candidate and asked for translation review, but nothing has made it to the released version.
Maybe there's something in the translation flow that we are doing wrong. I'm starting to miss the good old days when Mailman 2 translators just downloaded the .po files and returned them :-)
Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in < https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en
and submit a merge request to add them to a mailman/templates/es/ directory.
I will make the template translations locally, test them, and then, if they are yet lacking in the main repo, follow your suggestion.
I'm a bit short on time, but I'll help Guillermo with that, at least reviewing or doing a second pass. I'm not proficient enough to speak about Mailman core templates, but for Django templates, there is a nice tag for marking text with translations in the .mo files ...
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
On Sun, Feb 14, 2021 at 01:08, Victoriano Giralt <victoriano@uma.es> wrote:
El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió:
What translations are those? Please give specific examples. What I am saying is Mailman core 3.3.3 is currently up to date with weblate. There are no Spanish translations for core done after 7 November in weblate and weblate shows 100% completion for Spanish for Mailman core.
Mark, please, how do you check when translations happened? Nov 7th is a very significant date for me (it is my wedding anniversary) and I'm 90% sure that I dedicated time to Weblate after that date...
You can look at the commit history of the spanish po file to get a detailed history of when and who made the changes. For example:
Core: <https://gitlab.com/mailman/mailman/-/commits/master/src/mailman/messages/es/...> Postorius: <https://gitlab.com/mailman/postorius/-/commits/master/src/postorius/locale/e...>
You find similar histories in all the repos. Each person's changes should be an individual commit in the repo, typically all outstanding translations are committed every night in Weblate.
All strings related to Mailman (core, django_mailman3, postorius and hyperkitty) are translated into Spanish 100%, but the interfaces, after updating to the latest releases, are still in Englanish (more English than Spanish).
Could this be because of the .mo files not being up-to-update? There used to be some strings that were translated incorrectly, but I think we fixed all of those that we found.
Abhilash
This is not a fight, we want to help, but do not know how.
Thanks!
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> thanks, Abhilash Raj
On Sun, Feb 14, 2021 at 00:57, Victoriano Giralt <victoriano@uma.es> wrote:
El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) via Mailman-users escribió:
On 13/2/21 20:00, Mark Sapiro wrote:
But... here is a thing that I can not understand: If the source (the .po file) is from november 7th, it doesn't matter how many times you recompile it: the result will be the same. Correct, but the point is if you download the latest gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file in the distribution, you will find they are identical, so it it appears
On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: that the weblate translation hasn't changed since that time.
If there are issues in this mailman.po, they exist in weblate too and need to be fixed there.
That clarifies all. Thanks. As I said in my previous message, I'll wait for the next upgrade and hopingly the translations done after 7h of november (by others and me) will be there.
I've visited Weblate, all Spanish strings are translated. Spanish is 100% translated, but, none of them have been "approved", whatever that is. It seems that a reviewer needs to approve the translation in order for them to be incorporated or released or whatever. I was sure I had reviewed everything between November 7th and the day Abhilash announced the release candidate and asked for translation review, but nothing has made it to the released version.
Maybe there's something in the translation flow that we are doing wrong. I'm starting to miss the good old days when Mailman 2 translators just downloaded the .po files and returned them :-)
Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <
<https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en>
and submit a merge request to add them to a mailman/templates/es/ directory.
I will make the template translations locally, test them, and then, if they are yet lacking in the main repo, follow your suggestion.
I'm a bit short on time, but I'll help Guillermo with that, at least reviewing or doing a second pass. I'm not proficient enough to speak about Mailman core templates, but for Django templates, there is a nice tag for marking text with translations in the .mo files ...
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Victoriano Giralt writes:
I've visited Weblate, all Spanish strings are translated. Spanish is 100% translated, but, none of them have been "approved", whatever that is. It seems that a reviewer needs to approve the translation in order for them to be incorporated or released or whatever. I was sure I had reviewed everything between November 7th and the day Abhilash announced the release candidate and asked for translation review, but nothing has made it to the released version.
Maybe there's something in the translation flow that we are doing wrong. I'm starting to miss the good old days when Mailman 2 translators just downloaded the .po files and returned them :-)
Probably all it needs is for someone other than the submitter to check a box. I doubt there is an assigned reviewer/owner, just any translator registered for that language. That's the way Debian used to work, anyway, and it seems like a good way for open source to work.
@Abhilash, you set up Weblate, right? Do you know anything about this?
On Sat, Feb 13, 2021, at 9:21 PM, Stephen J. Turnbull wrote:
Victoriano Giralt writes:
I've visited Weblate, all Spanish strings are translated. Spanish is 100% translated, but, none of them have been "approved", whatever that is. It seems that a reviewer needs to approve the translation in order for them to be incorporated or released or whatever. I was sure I had reviewed everything between November 7th and the day Abhilash announced the release candidate and asked for translation review, but nothing has made it to the released version.
Maybe there's something in the translation flow that we are doing wrong. I'm starting to miss the good old days when Mailman 2 translators just downloaded the .po files and returned them :-)
Probably all it needs is for someone other than the submitter to check a box. I doubt there is an assigned reviewer/owner, just any translator registered for that language. That's the way Debian used to work, anyway, and it seems like a good way for open source to work.
@Abhilash, you set up Weblate, right? Do you know anything about this?
https://docs.weblate.org/en/latest/workflows.html
This is the documentation from Weblate about the whole workflow. There is a Project level setting which mandates that a Reviewer review and approve all the translated strings, but that is turned off for GNU Mailman project.
-- thanks, Abhilash Raj (maxking)
On Sat, Feb 13, 2021 at 11:00, Mark Sapiro <mark@msapiro.net> wrote:
On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
But... here is a thing that I can not understand: If the source (the .po file) is from november 7th, it doesn't matter how many times you recompile it: the result will be the same.
Correct, but the point is if you download the latest gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file in the distribution, you will find they are identical, so it it appears that the weblate translation hasn't changed since that time.
If there are issues in this mailman.po, they exist in weblate too and need to be fixed there.
Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <<https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en>> and submit a merge request to add them to a mailman/templates/es/ directory.
You can actually translate the templates in Weblate too. That is actually the whole reason to go with monolingual template format in Mailman Core.
Mailman uses the template file's name as the msgid for translations and all in-tree templates are copied into English's .po file when we re-generate them.
For example in here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC_...
The english .po file is considered as reference in Weblate and used for source string.
Abhilash
On 2/13/21 5:42 PM, Abhilash Raj wrote:
You can actually translate the templates in Weblate too. That is actually the whole reason to go with monolingual template format in Mailman Core.
Mailman uses the template file's name as the msgid for translations and all in-tree templates are copied into English's .po file when we re-generate them.
For example in here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC_...
The english .po file is considered as reference in Weblate and used for source string.
But it appears that we are lacking a mechanism (other than some manual process which isn't reliably done) to move the translated templates from the translated .po file to the appropriate templates/<lc>/ directory.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, Feb 13, 2021, at 9:26 PM, Mark Sapiro wrote:
On 2/13/21 5:42 PM, Abhilash Raj wrote:
You can actually translate the templates in Weblate too. That is actually the whole reason to go with monolingual template format in Mailman Core.
Mailman uses the template file's name as the msgid for translations and all in-tree templates are copied into English's .po file when we re-generate them.
For example in here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC_...
The english .po file is considered as reference in Weblate and used for source string.
But it appears that we are lacking a mechanism (other than some manual process which isn't reliably done) to move the translated templates from the translated .po file to the appropriate templates/<lc>/ directory.
Yeah, you are absolutely right. I thought in my head that I had modified the lookup mechanism to use gettext for in-source templates, but that doesn't seem to be the case.
https://gitlab.com/mailman/mailman/-/issues/825
I have opened an issue to track that.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
On 14/2/21 2:42, Abhilash Raj wrote:
You can actually translate the templates in Weblate too. That is actually the whole reason to go with monolingual template format in Mailman Core.
Mailman uses the template file's name as the msgid for translations and all in-tree templates are copied into English's .po file when we re-generate them.
For example in here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC_...
The english .po file is considered as reference in Weblate and used for source string.
I want to contribute making it via Weblate, since it is already done via gitlab repository (thanks to Mark Sapiro for approving the merge requests), making a revision and editing them if needed, but I cannot see how to make it in a consistent way, as I cannot determine how to edit each template in the Weblate UI. I've tried to access via the file name (accessing via msgid as for your example) of the template... but I cannot access them by this way, or I'm missing something.
Can you, please, point me in the right direction on how to do it?
On 18/2/21 9:13, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 14/2/21 2:42, Abhilash Raj wrote:
You can actually translate the templates in Weblate too. That is actually the whole reason to go with monolingual template format in Mailman Core.
Mailman uses the template file's name as the msgid for translations and all in-tree templates are copied into English's .po file when we re-generate them.
For example in here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC_...
The english .po file is considered as reference in Weblate and used for source string.
I want to contribute making it via Weblate, since it is already done via gitlab repository (thanks to Mark Sapiro for approving the merge requests), making a revision and editing them if needed, but I cannot see how to make it in a consistent way, as I cannot determine how to edit each template in the Weblate UI. I've tried to access via the file name (accessing via msgid as for your example) of the template... but I cannot access them by this way, or I'm missing something.
Can you, please, point me in the right direction on how to do it?
Forget this, I've just found how to do it. Selecting by "key/context" and the name of the file seems to do the trick.
Movin' on
Sorry for the noise.
On 18/2/21 11:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
I want to contribute making it via Weblate, since it is already done via gitlab repository (thanks to Mark Sapiro for approving the merge requests), making a revision and editing them if needed, but I cannot see how to make it in a consistent way, as I cannot determine how to edit each template in the Weblate UI. I've tried to access via the file name (accessing via msgid as for your example) of the template... but I cannot access them by this way, or I'm missing something.
Can you, please, point me in the right direction on how to do it?
Forget this, I've just found how to do it. Selecting by "key/context" and the name of the file seems to do the trick.
Done. Now the Weblate translation of templates is consistent with the gitlab src repository.
On 2/18/21 3:57 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
Done. Now the Weblate translation of templates is consistent with the gitlab src repository.
Thank you for your work on this. It is much appreciated.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 13/2/21 20:00, Mark Sapiro wrote:
Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> and submit a merge request to add them to a mailman/templates/es/ directory.
I downladed the templates and I'm beginning the translation process, but I have a question. What language map has to be used? In my S.O. it's ISO-8859-15 but I'm concerned it has to be UTF-8... Better ask before having to do a remapping of the files after...
It comes to my attention that three files have 0 bytes.
-rw-r--r-- 1 Oldno7 wheel 382 14 feb. 00:22 domain:admin:notice:new-list.txt -rw-r--r-- 1 Oldno7 wheel 886 15 feb. 11:28 help.txt -rw-r--r-- 1 Oldno7 wheel 289 14 feb. 00:22 list:admin:action:post.txt -rw-r--r-- 1 Oldno7 wheel 120 14 feb. 00:22 list:admin:action:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 122 14 feb. 00:22 list:admin:action:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 133 14 feb. 00:22 list:admin:notice:disable.txt -rw-r--r-- 1 Oldno7 wheel 71 14 feb. 00:22 list:admin:notice:removal.txt -rw-r--r-- 1 Oldno7 wheel 59 14 feb. 00:22 list:admin:notice:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 257 14 feb. 00:22 list:admin:notice:unrecognized.txt -rw-r--r-- 1 Oldno7 wheel 45 14 feb. 00:22 list:admin:notice:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:member:digest:header.txt -rw-r--r-- 1 Oldno7 wheel 337 14 feb. 00:22 list:member:digest:masthead.txt -rw-r--r-- 1 Oldno7 wheel 154 14 feb. 00:22 list:member:generic:footer.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:member:regular:header.txt -rw-r--r-- 1 Oldno7 wheel 562 14 feb. 00:22 list:user:action:invite.txt -rw-r--r-- 1 Oldno7 wheel 753 14 feb. 00:22 list:user:action:subscribe.txt -rw-r--r-- 1 Oldno7 wheel 739 14 feb. 00:22 list:user:action:unsubscribe.txt -rw-r--r-- 1 Oldno7 wheel 0 14 feb. 00:22 list:user:notice:goodbye.txt -rw-r--r-- 1 Oldno7 wheel 281 14 feb. 00:22 list:user:notice:hold.txt -rw-r--r-- 1 Oldno7 wheel 439 14 feb. 00:22 list:user:notice:no-more-today.txt -rw-r--r-- 1 Oldno7 wheel 98 14 feb. 00:22 list:user:notice:post.txt -rw-r--r-- 1 Oldno7 wheel 568 14 feb. 00:22 list:user:notice:probe.txt -rw-r--r-- 1 Oldno7 wheel 273 14 feb. 00:22 list:user:notice:refuse.txt -rw-r--r-- 1 Oldno7 wheel 151 14 feb. 00:22 list:user:notice:rejected.txt -rw-r--r-- 1 Oldno7 wheel 353 14 feb. 00:22 list:user:notice:warning.txt -rw-r--r-- 1 Oldno7 wheel 532 14 feb. 00:22 list:user:notice:welcome.txt
TIA.
On 2/15/21 2:38 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
On 13/2/21 20:00, Mark Sapiro wrote:
Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en>
and submit a merge request to add them to a mailman/templates/es/ directory.
I downladed the templates and I'm beginning the translation process, but I have a question. What language map has to be used? In my S.O. it's ISO-8859-15 but I'm concerned it has to be UTF-8... Better ask before having to do a remapping of the files after...
They should be encoded as UTF-8.
It comes to my attention that three files have 0 bytes.
The 0-byte files can either be left out of templates/es or put in as empty files. They are things for templates which are empty by default.
Also, help.txt is unused and doesn't need to be translated. At one time
it was intended to be the template for the response to the email help
command, but it is not used for that purpose.
Finally, although I said previously that the translated templates should be submitted as a merge request, that can still be done, but is not necessary. They can be translated in weblate. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...> and <https://gitlab.com/mailman/mailman/-/issues/825>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 15/2/21 16:57, Mark Sapiro wrote:
Finally, although I said previously that the translated templates should be submitted as a merge request, that can still be done, but is not necessary. They can be translated in weblate. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...> and<https://gitlab.com/mailman/mailman/-/issues/825>.
I had the templates translated now in UTF-8 coding map. I copied all of them en a new directory (es) under mailman package templates (as I can see are other languages):
/usr/local/lib/python3.7/site-packages/mailman # ls templates __init__.py de es it __pycache__ en fr sk
/usr/local/lib/python3.7/site-packages/mailman # ls templates/es domain:admin:notice:new-list.txt list:member:regular:header.txt help.txt list:user:action:invite.txt list:admin:action:post.txt list:user:action:subscribe.txt list:admin:action:subscribe.txt list:user:action:unsubscribe.txt list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt list:admin:notice:disable.txt list:user:notice:hold.txt list:admin:notice:removal.txt list:user:notice:no-more-today.txt list:admin:notice:subscribe.txt list:user:notice:post.txt list:admin:notice:unrecognized.txt list:user:notice:probe.txt list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt list:member:digest:header.txt list:user:notice:rejected.txt list:member:digest:masthead.txt list:user:notice:warning.txt list:member:generic:footer.txt list:user:notice:welcome.txt
But mailman isn't aware of them (I restarted the server). May I have to execute some process as "compilemessages" to mailman be capable to use them? Now mailman is using the "en" templates for sure.
After testing them I'll do both of the suggestionsyou made: a merge request AND the revision and translation via Weblate.
On 2/16/21 2:59 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
/usr/local/lib/python3.7/site-packages/mailman # ls templates/es domain:admin:notice:new-list.txt list:member:regular:header.txt help.txt list:user:action:invite.txt list:admin:action:post.txt list:user:action:subscribe.txt list:admin:action:subscribe.txt list:user:action:unsubscribe.txt list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt list:admin:notice:disable.txt list:user:notice:hold.txt list:admin:notice:removal.txt list:user:notice:no-more-today.txt list:admin:notice:subscribe.txt list:user:notice:post.txt list:admin:notice:unrecognized.txt list:user:notice:probe.txt list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt list:member:digest:header.txt list:user:notice:rejected.txt list:member:digest:masthead.txt list:user:notice:warning.txt list:member:generic:footer.txt list:user:notice:welcome.txt
But mailman isn't aware of them (I restarted the server). May I have to execute some process as "compilemessages" to mailman be capable to use them? Now mailman is using the "en" templates for sure.
Does Mailman have permission to search the templates/es directory and read the templates? Are there overriding templates in Mailman's var/templates/ directory?
Are you sure your tests access the templates in a Spanish language context?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 16/2/21 22:47, Mark Sapiro wrote:
On 2/16/21 2:59 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
/usr/local/lib/python3.7/site-packages/mailman # ls templates/es domain:admin:notice:new-list.txt list:member:regular:header.txt help.txt list:user:action:invite.txt list:admin:action:post.txt list:user:action:subscribe.txt list:admin:action:subscribe.txt list:user:action:unsubscribe.txt list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt list:admin:notice:disable.txt list:user:notice:hold.txt list:admin:notice:removal.txt list:user:notice:no-more-today.txt list:admin:notice:subscribe.txt list:user:notice:post.txt list:admin:notice:unrecognized.txt list:user:notice:probe.txt list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt list:member:digest:header.txt list:user:notice:rejected.txt list:member:digest:masthead.txt list:user:notice:warning.txt list:member:generic:footer.txt list:user:notice:welcome.txt
But mailman isn't aware of them (I restarted the server). May I have to execute some process as "compilemessages" to mailman be capable to use them? Now mailman is using the "en" templates for sure. Does Mailman have permission to search the templates/es directory and read the templates? They have exactly the same permissions that the other templates directories. Are there overriding templates in Mailman's var/templates/ directory? Not at all.
Are you sure your tests access the templates in a Spanish language context?
Yes, I think so, but it could be that I'm missing something here. I double check this tomorrow as for your answer It seems there is no ulterior process as with messages.
Anyway, I could just substitute all the en templates, but it's not the way to maintain language flexibility, you know :)
Thanks for your answer
P.S.: anyway, I did a merge request in gitlab as you advised.
On 2/16/21 2:04 PM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
P.S.: anyway, I did a merge request in gitlab as you advised.
But your MR <https://gitlab.com/mailman/mailman/-/merge_requests/780> didn't actually add the templates, so I created <https://gitlab.com/mailman/mailman/-/merge_requests/781> and merged it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 16/2/21 23:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
Are you sure your tests access the templates in a Spanish language context?
Yes, I think so, but it could be that I'm missing something here. I double check this tomorrow as for your answer It seems there is no ulterior process as with messages.
It was it. The list I was using to test the messages and templates was not configured as "spanish". It's a test list that I newly configured when I migrated to mailman3.
I've just suscribed a new member in other list and the notification is using the spanish template I translated.
On Sat, 2021-02-13 at 17:04 +0900, Stephen J. Turnbull wrote:
Your English is fine, it was just my lack of imagination: on February 12, I couldn't conceive of February 3 being even a little "old"!
I was not your imagination, it was confussion inserted in the line between brain and fingers and I meant .po and wrote .mo
More important, as long as the .mo file is more recent than the .po file, that's the best the release manager can do. I haven't been involved in the release process, so I can't swear to it personally, but if Mark says that new translations generate a merge request automatically, and we make sure that the translations are merged before release, I believe him. That's optimal as far I am concerned.
But, it seems something did not go well :-(
Perhaps some enterprising soul would be willing to automate production of pip'able packages containing only new translations, but without that, I don't see how to beat our current procedures. (I wouldn't want to use such a thing, though, I'd be too afraid that one day all the translations would be replaced with Dril tweets!)
Fully agreed. I first thought of "language chanpions" that could take care of syncing the .po files from Weblate to the replease repository. But then, that involves human availability, which is not an abundant asset in open source projects.
Then, my brains went into "crazy mode", why do notuse the power of Python and the net. Maybe we can get someone (GSoC student) to write code that, given a .po file uses Google translation to check that the resulting string in the target language means more or less the same as the original English string on the .po file?
Crazy-tinking-ly, Victoriano.
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?
participants (5)
-
Abhilash Raj -
Guillermo Hernandez (Oldno7) -
Mark Sapiro -
Stephen J. Turnbull -
Victoriano Giralt