WebFrontend language not working
Hello,
I am using mailman3 as list owner on python.org.
The web-frontend shows me everything in "German" which is my native language (in OS, Browser, GeoIP). But I want it in English. in my "Global Mailman-Settings" the "Preferred Language ( "Bevorzugte Sprache" ) is set to "English (USA)". But it seems to me that this doesn't affect the WebFront end.
How can set the WebFront end to English?
Kind Christian
On 6/5/22 13:36, c.buhtz@posteo.jp wrote:
Hello,
I am using mailman3 as list owner on python.org.
The web-frontend shows me everything in "German" which is my native language (in OS, Browser, GeoIP). But I want it in English. in my "Global Mailman-Settings" the "Preferred Language ( "Bevorzugte Sprache" ) is set to "English (USA)". But it seems to me that this doesn't affect the WebFront end.
How can set the WebFront end to English?
Tell your browser that your preferred language is English.
The web UI is based on Django and Django gets your locale from your browser.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Dear Mark,
thanks for the reply.
On 2022-06-05 15:37 Mark Sapiro mark@msapiro.net wrote:
Tell your browser that your preferred language is English.
No I won't. I want the mailman3 interface in English not all content from my browser.
The web UI is based on Django and Django gets your locale from your browser.
Than this is a (design) bug in Django. But I assume that Django is able to overwrite this behavior. You just have to use that feature.
There is an open Issue about the problem.
As always, patches are welcome. Since apparently nobody in core knows about the Django feature you suggest "must" exist, this is going to be low priority unless a patch is submitted, sorry.
c.buhtz@posteo.jp writes:
There is an open Issue about the problem.
https://gitlab.com/mailman/hyperkitty/-/issues/337
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/
Dear Stephen,
no need to say sorry for this. It is FOSS. Opening an Issue doesn't mean it has to be fixed/improved at the same time. There are several good reasons to keep Issues open (for years).
So please don't feel pressure. For most of us (contributors, core devs and users) it is just free time we invest. Everyone knows.
But not OK is to send duplicates via a mailing list especially when it is the mailman list itself. You know about your "munging" feature? ;)
And also the "patches are welcome" is IMHO also not a good habit. I assume you didn't mean it inpolite but users often treat it like that. It put users under pressure also. It sounds a bit like "get your #?!§$ done by yourself.". This will keep users away from reporting bugs and features.
Kind Christian
On 2022-06-06 20:22 "Stephen J. Turnbull" stephenjturnbull@gmail.com wrote:
As always, patches are welcome. Since apparently nobody in core knows about the Django feature you suggest "must" exist, this is going to be low priority unless a patch is submitted, sorry.
c.buhtz@posteo.jp writes:
There is an open Issue about the problem.
https://gitlab.com/mailman/hyperkitty/-/issues/337
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/
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/
participants (3)
-
c.buhtz＠posteo.jp -
Mark Sapiro -
Stephen J. Turnbull