Translation (Localization) of mail addresses?

Are there any plans to support changing of mail interface addresses for other languages?
In MTA/Utils.py I find: ('admin', 'bounces', 'confirm', 'join', 'leave', 'owner', 'request', 'subscribe', 'unsubscribe'): Should the Italian mail extensions be something like: gestire rimbalzi confermare aderire partire proprietario richiesta sottoscrivi annulla?
In the future could someone unsubscribe from terrier@dogs.us or terrier@cane.it with mail to: terrier-unsubscribe@dogs.us or terrier-annulla@cane.it
Yes, I can do it in the mail system interface now but will Mailman ever want control over those mail addresses? Some of the mail addresses are listed in the help messages for example.
Right now the above list is hardwired in places outside of Utils.py. It would be cleaner if there was a documented way for me to get the list of extensions.
Ciao,
//Z\\

Jim Ziobro writes:
Are there any plans to support changing of mail interface addresses for other languages?
No. There won't be, and patches submitted will very likely be rejected.
No. These aren't English words. They're magic strings (like HTML tags or programming keywords), which are embedded in many clients, including personal and organizational web pages (with RFC 2368 mailto URLs). "request" is specified by RFC 2142. The others are common aliases for functions that are mostly also available via the -request address. -bounces is entirely Mailman-specific; neither you nor any user should need to know about it unless things get really horked.
In fact, users should not need to know any of them. The translations you suggest can and should be in client user interfaces, not the wire protocol.
Mark has the final say, but I'd bet my house he's gonna say "no, not in Mailman 2".
It's mostly not a Mailman issue. It wouldn't be that hard for us to do it (but such work won't be done on Mailman 2). The PITA would be all the complaints we get from users who send mail to terrier-anulla@dogs.us or terrier-unsubscribe@cane-it. (I would oppose doing it on Mailman 3 as a waste of time and an attractive nuisance.)
The way the world is going these days, the only one of those addresses that's likely to actually get used is -confirm (which is necessary because it's used in the proof of mailbox ownership dialog). Users generally prefer to interact with the website, and admins like to encourage that, because that gives them control over what the users can actually do to interact with Mailman, unlike email where they can (and do) insane stuff.
Steve

On 12/5/18 9:28 PM, Jim Ziobro wrote:
Are there any plans to support changing of mail interface addresses for other languages?
Steve has already replied in detail and I agree with what he has said.
For Mailman 2.1, No localization of the address suffixes will be done.
For Mailman 3, it is not solely up to me, but I wouldn't do it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On Thu, 6 Dec 2018, Jim Ziobro wrote:
Are there any plans to support changing of mail interface addresses for other languages?
As a native italian speaker (who however virtually always uses the English interface in the *GUI* of mailman and any other tool) I would regard as highly inconvenient any localization of *service address suffixes*).
First of all admins may be used to the English-like form and would be annoyed to use a different form for different mailing lists
Secondly it would be like translating commands in a programming language ... GO TO -> VAI A (Fortran), if -> se (almost all languages), open -> apri (C and other languages) ... nobody does that seriously but for fun !
Finally, in lack of an agreed standard, since Italian is a much more complicated language for what concerns verbal forms, one will have to choose the tense (infinitive, imperative or indicative) and the person (2nd singular, 2nd plural or 3rd courtesy form), Just crazy.
-- Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html
"All that is google does not glitter Nor all who use alpine/procmail are lost"

On 12/06/2018 11:24 AM, Lucio Chiappetti wrote:
Oh, I dunno. I think "почтальон-отскакивет" sounds hilarious in Russian. (Google translation, although incorrect, ain't bad either.) I see great fun potential.
-- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

Jim Ziobro writes:
Are there any plans to support changing of mail interface addresses for other languages?
No. There won't be, and patches submitted will very likely be rejected.
No. These aren't English words. They're magic strings (like HTML tags or programming keywords), which are embedded in many clients, including personal and organizational web pages (with RFC 2368 mailto URLs). "request" is specified by RFC 2142. The others are common aliases for functions that are mostly also available via the -request address. -bounces is entirely Mailman-specific; neither you nor any user should need to know about it unless things get really horked.
In fact, users should not need to know any of them. The translations you suggest can and should be in client user interfaces, not the wire protocol.
Mark has the final say, but I'd bet my house he's gonna say "no, not in Mailman 2".
It's mostly not a Mailman issue. It wouldn't be that hard for us to do it (but such work won't be done on Mailman 2). The PITA would be all the complaints we get from users who send mail to terrier-anulla@dogs.us or terrier-unsubscribe@cane-it. (I would oppose doing it on Mailman 3 as a waste of time and an attractive nuisance.)
The way the world is going these days, the only one of those addresses that's likely to actually get used is -confirm (which is necessary because it's used in the proof of mailbox ownership dialog). Users generally prefer to interact with the website, and admins like to encourage that, because that gives them control over what the users can actually do to interact with Mailman, unlike email where they can (and do) insane stuff.
Steve

On 12/5/18 9:28 PM, Jim Ziobro wrote:
Are there any plans to support changing of mail interface addresses for other languages?
Steve has already replied in detail and I agree with what he has said.
For Mailman 2.1, No localization of the address suffixes will be done.
For Mailman 3, it is not solely up to me, but I wouldn't do it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On Thu, 6 Dec 2018, Jim Ziobro wrote:
Are there any plans to support changing of mail interface addresses for other languages?
As a native italian speaker (who however virtually always uses the English interface in the *GUI* of mailman and any other tool) I would regard as highly inconvenient any localization of *service address suffixes*).
First of all admins may be used to the English-like form and would be annoyed to use a different form for different mailing lists
Secondly it would be like translating commands in a programming language ... GO TO -> VAI A (Fortran), if -> se (almost all languages), open -> apri (C and other languages) ... nobody does that seriously but for fun !
Finally, in lack of an agreed standard, since Italian is a much more complicated language for what concerns verbal forms, one will have to choose the tense (infinitive, imperative or indicative) and the person (2nd singular, 2nd plural or 3rd courtesy form), Just crazy.
-- Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html
"All that is google does not glitter Nor all who use alpine/procmail are lost"

On 12/06/2018 11:24 AM, Lucio Chiappetti wrote:
Oh, I dunno. I think "почтальон-отскакивет" sounds hilarious in Russian. (Google translation, although incorrect, ain't bad either.) I see great fun potential.
-- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
participants (5)
-
Dimitri Maziuk
-
Jim Ziobro
-
Lucio Chiappetti
-
Mark Sapiro
-
Stephen J. Turnbull