Hey, I set up Mailman3 from the Debian-packages and got it working.
But for some reason I do have a mixed setup in languages now. Some strings are in English, some are in German. The settings I changed are:
in mailman.cfg [mailman] default_language: de
in mailman-web.py LANGUAGE_CODE = 'de-DE' TIME_ZONE = 'Europe/Berlin'
Nothing changed after restarting services.
I then came across this post: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/X... -> but actually I do not find any of the files, ...
- no mailman.po / .mo
- no generate_mo.sh
- no languages folders in /usr/lib/python3/dist-packages/mailman/messages
- when searching with locate (after updatedb) no LC_MESSAGES/mailman or anything stated in the post
Actually it would be fantastic to be able to choose language for the web interface / lists like on this here, but this is additional :-) just to have it in one language, this time German would be cool. I also would translate, but it seems finished: https://hosted.weblate.org/projects/gnu-mailman/mailman/
Thank you for help, regards, Jens.
- Jens Günther (jens.guenther@posteo.de) [210319 15:29]:
But for some reason I do have a mixed setup in languages now. Some strings are in English, some are in German. The settings I changed are:
which package version do you use?
Actually I would recommend using the packages from bullseye for mailman3. This should work with e.g. some pinning.
(I'm thinking if we should try to get mailman3 into stable-backports, because that might be actually useful.)
Also, translations had been the reason for some discussions lately, so this is still some work-in-progress. (Also on the git version I'm using, there are more texts in English than I'd wish for.)
Andi
Hey, thanks for the quick reply.
Am 19.03.21 um 15:44 schrieb Andreas Barth:
- Jens Günther (jens.guenther@posteo.de) [210319 15:29]:
But for some reason I do have a mixed setup in languages now. Some strings are in English, some are in German. The settings I changed are:
which package version do you use?
I do use the ones from buster, yes, so it's running mailman3-version 3.2.1
Actually I would recommend using the packages from bullseye for mailman3. This should work with e.g. some pinning.
You think it's ok to install from testing? I have already the bullseye-package with a lower preference then the stable ones, so I could do so, advertises version 3.3.3 there ... but always try to stick with stable packages :-) never know. With the backports I often do go along, but never know what testing does, when you start with a mixed system...
If so, do you know how to do to install all needed dependencies correctly!? 'apt install mailman3-full -t bullseye' shouldn't be all of it, no!?
(I'm thinking if we should try to get mailman3 into stable-backports, because that might be actually useful.)
Also, translations had been the reason for some discussions lately, so this is still some work-in-progress. (Also on the git version I'm using, there are more texts in English than I'd wish for.)
What I hear is that this is a common issue and I probably should get along with it for now!?
Andi
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/
- Jens Günther (jens.guenther@posteo.de) [210319 15:58]:
You think it's ok to install from testing? I have already the bullseye-package with a lower preference then the stable ones, so I could do so, advertises version 3.3.3 there ... but always try to stick with stable packages :-) never know. With the backports I often do go along, but never know what testing does, when you start with a mixed system...
Well, I personally wouldn't be so afraid, but that might come from the fact that I know the debian ecosystem way too well :)
If all in all the stable package works for you, I would always recommend to stick with the stable version. If not, the testing version could be an option. As disclaimer, I'm using the version from git, but I decided so because I expected that I need to change code and that's easier from the git version.
Other people here have other recommendations (i.e. always recommend to work with the git versions), but that's the usual differences. In the end, please just use what fits best for you.
If so, do you know how to do to install all needed dependencies correctly!? 'apt install mailman3-full -t bullseye' shouldn't be all of it, no!?
Without having it tried myself, that should do the trick.
Also, translations had been the reason for some discussions lately, so this is still some work-in-progress. (Also on the git version I'm using, there are more texts in English than I'd wish for.)
What I hear is that this is a common issue and I probably should get along with it for now!?
Well, let's say: some important fixes had been made in the git tree recently (but I forgot if before or after the latest release), so situation should improve sooner or later.
mailman3 is under active development, which has both the advantage and disadvantage that things are changing.
Andi
Ist actually working that well here on this list that well because of the newer version? https://lists.mailman3.org/mailman3/
What are the hints, who is actually running the list!? :-)
And how is it done to be able to change the language that nicely?
Am 19.03.21 um 16:13 schrieb Andreas Barth:
Also, translations had been the reason for some discussions lately, so this is still some work-in-progress. (Also on the git version I'm using, there are more texts in English than I'd wish for.) What I hear is that this is a common issue and I probably should get along with it for now!? Well, let's say: some important fixes had been made in the git tree recently (but I forgot if before or after the latest release), so situation should improve sooner or later.
mailman3 is under active development, which has both the advantage and disadvantage that things are changing.
Andreas Barth writes:
Well, I personally wouldn't be so afraid, but that might come from the fact that I know the debian ecosystem way too well :)
FWIW I've run a testing + a very few pinned to sid[1] for 15 years now, and never had unexpected problems with testing packages themselves, and only very rarely with distro issues (mucked up dependencies where I couldn't install the current version of some package as specified in testing).
J. Guenther writes:
Also, translations had been the reason for some discussions lately, so this is still some work-in-progress. (Also on the git version I'm using, there are more texts in English than I'd wish for.)
What I hear is that this is a common issue and I probably should get along with it for now!?
As Andi says, there was a glitch in the Weblate (IIRC) to Mailman sources pipeline which should be fixed now, but for specific languages you kind of have to track the completion rate with that translation community. Probably there's a way to check on Weblate itself. If Weblate seems to be much farther along than Mailman git, ping us, it's still a pretty manual process.
Regards, Steve
Footnotes: [1] These are all applications that I had extensive experience with install from source, and still want quite recent versions.
On Mar 20, 2021, at 10:19 AM, Stephen J. Turnbull <turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
Andreas Barth writes:
Well, I personally wouldn't be so afraid, but that might come from the fact that I know the debian ecosystem way too well :)
FWIW I've run a testing + a very few pinned to sid[1] for 15 years now, and never had unexpected problems with testing packages themselves, and only very rarely with distro issues (mucked up dependencies where I couldn't install the current version of some package as specified in testing).
J. Guenther writes:
Also, translations had been the reason for some discussions lately, so this is still some work-in-progress. (Also on the git version I'm using, there are more texts in English than I'd wish for.)
What I hear is that this is a common issue and I probably should get along with it for now!?
As Andi says, there was a glitch in the Weblate (IIRC) to Mailman sources pipeline which should be fixed now, but for specific languages you kind of have to track the completion rate with that translation community. Probably there's a way to check on Weblate itself.
Yeah, you can go the project page on Weblate and check completion rate for a specific language. For example this is the page for Postorius.
https://hosted.weblate.org/projects/gnu-mailman/postorius/
If Weblate seems to be much farther along than Mailman git, ping us, it's still a pretty manual process.
For web interface (Postorius, django-mailman3 and Hyperkitty) it is only manual to the point that someone has to click “Merge” ;-) The process is fairly automated and new translations are sent as Merge Request[1] against our Git repos nightly.
Since each commit adds a Merge Commit, I sometimes wait a little for 4-5 commits to pile up before merging them. But if there are large number of people installing from Git for up-to-date translations, I wouldn’t mind merging them asap.
We definitely merge everything before a release is made and translations in a released version will definitely lag behind the Weblate for any changes made after the release.
Core has a bit of manual work needed to copy translations from .po files to actual template files (.txt), but hopefully I or someone else will be able to fix that soon. It just needs a script to read from all the language specific .po files and write the translated templates to individual .txt files (where Core expects them to be).
[1]: Like this one, for example, https://gitlab.com/mailman/postorius/-/merge_requests/618
Regards, Steve
Footnotes: [1] These are all applications that I had extensive experience with install from source, and still want quite recent versions.
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)
For web interface (Postorius, django-mailman3 and Hyperkitty) it is only manual to the point that someone has to click “Merge” ;-) The process is fairly automated and new translations are sent as Merge Request[1] against our Git repos nightly.
Since each commit adds a Merge Commit,
What I meant to say was, each Merge Request adds a merge commit.
-- thanks, Abhilash Raj (maxking)
participants (4)
-
Abhilash Raj -
Andreas Barth -
Jens Günther -
Stephen J. Turnbull