From barco at atservice.co.za Thu Feb 2 14:55:18 2017 From: barco at atservice.co.za (Barco van Rhijn) Date: Thu, 2 Feb 2017 21:55:18 +0200 Subject: [Mailman-i18n] Translating listname-request and other functions Message-ID: <8186d869-34aa-920f-878f-e39753ccd8be@atservice.co.za> Hi Everyone, Is there a way to translate email addresses used for commands like listname-request listname-bounces Warm Regards Barco From mark at msapiro.net Thu Feb 2 15:25:15 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 2 Feb 2017 12:25:15 -0800 Subject: [Mailman-i18n] Translating listname-request and other functions In-Reply-To: <8186d869-34aa-920f-878f-e39753ccd8be@atservice.co.za> References: <8186d869-34aa-920f-878f-e39753ccd8be@atservice.co.za> Message-ID: <044946d4-f167-47b1-4929-b6ae6a031d69@msapiro.net> On 02/02/2017 11:55 AM, Barco van Rhijn wrote: > > Is there a way to translate email addresses used for commands like > listname-request > listname-bounces No. Mailman isn't set up to internationalize those addresses. There would be several issues in trying to do so. Not only would you have to find everywhere where those strings appear and replace the string with an i18n lookup, you'd also have to ensure that the translation of 'bounces', 'request' etc. didn't contain any characters that aren't allowed in email addresses. Even if internationalized email addresses per RFC 6531 were used, the extensions (SMTPUTF8) to support this aren't universally implemented which can result in delivery issues. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From az at kth.se Tue Feb 7 11:14:20 2017 From: az at kth.se (Andreas Pettersson) Date: Tue, 7 Feb 2017 17:14:20 +0100 Subject: [Mailman-i18n] Swedish translation for GNU Mailman Message-ID: <3aa57e84-e834-4cc5-70d6-0c991e758fd2@kth.se> Hi, I like to contribute to the Swedish translation of GNU Mailman. Is there any newer translation, GNU Mailman 2.1 was last edited in 2002? /Andreas From mark at msapiro.net Tue Feb 7 11:53:02 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 7 Feb 2017 08:53:02 -0800 Subject: [Mailman-i18n] Swedish translation for GNU Mailman In-Reply-To: <3aa57e84-e834-4cc5-70d6-0c991e758fd2@kth.se> References: <3aa57e84-e834-4cc5-70d6-0c991e758fd2@kth.se> Message-ID: On 02/07/2017 08:14 AM, Andreas Pettersson wrote: > Hi, I like to contribute to the Swedish translation of GNU Mailman. Is > there any newer translation, GNU Mailman 2.1 was last edited in 2002? The latest templates are at and the message catalog is at . Other than a few template updates, little if anything has changed from the initial contribution. We welcome your help. If you haven't already seen it, gives information about submitting translations. There is other information at and linked from . If you have any questions, please ask on this list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From az at kth.se Sat Feb 11 18:35:01 2017 From: az at kth.se (Andreas Pettersson) Date: Sat, 11 Feb 2017 23:35:01 +0000 Subject: [Mailman-i18n] =?iso-8859-1?q?Letters_=E5=2C_=E4=2C_=F6?= Message-ID: <1486856104481.83173@kth.se> Hi, some strings uses å ä ö for ? ? ?. e.g. Non-digest options -> Inställningar för normalversion Is it still necessary? /Andreas -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at msapiro.net Sat Feb 11 22:35:01 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 11 Feb 2017 19:35:01 -0800 Subject: [Mailman-i18n] =?utf-8?b?TGV0dGVycyDDpSwgw6QsIMO2?= In-Reply-To: <1486856104481.83173@kth.se> References: <1486856104481.83173@kth.se> Message-ID: On 02/11/2017 03:35 PM, Andreas Pettersson wrote: > Hi, some strings uses å ä ö for ? ? ?. > > e.g. > > Non-digest options -> > > Inställningar för normalversion > > > Is it still necessary? Yes. It is problematic in the message catalog because it isn't always clear whether a string is used in a plain text context only, an html context only or both, but strings which are used in an html context only and html templates, as long as they are predominantly ascii should have non-ascii represented as html entities. This is to avoid the garbling that can occur in installations where the web server overrides the character encoding of a page. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan