-
Hi, I´m trying to translate listen to german. First approach was to generate a listen-de.po file and store it in a new folder i18n. I also put the file in locales/de/LC_MESSAGES/. Both resulted in a few translations on the website, but every email generated by listen is still in english. So I changed the Text in lib/ default_email_text.py. (which is of course a ugly hack) Now I´m getting the emails in german but every umlaut, like ÜÖÄ is messed up in the mail client. Of Course I double checked that my file is in correct encoding (utf-8) Also using the web "Invite new Members" function now results in an unicode error. Here is an example of an email: Return-Path: <testliste3@...> Subject: Subscription confirmation (mail-command:subscribe-member <<kai@XXX>> [50674187]) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MailBoxer Date: Wed, 04 Mar 2009 22:07:50 +0100 Hallo Kai, Wir haben eine Bestellungsanfrage für Ihre E-Mail Adresse für die So it seem to have a correct charset I also wonder how to change the magic subject words "subscribe" and "unsubscribe" Any help or push in the right direction would be welcome. Thanks Kai
-
On Thu, Mar 05, 2009 at 12:19:15AM +0100, Kai-Oliver Tiffany wrote: > Hi, > > I´m trying to translate listen to german. First approach was to > generate a listen-de.po file and store it in a new folder i18n. I also > put the file in locales/de/LC_MESSAGES/. Both resulted in a few > translations on the website, but every email generated by listen is > still in english. So I changed the Text in lib/default_email_text.py. > (which is of course a ugly hack) Now I´m getting the emails in german but > every umlaut, like ÜÖÄ is messed up in the mail client. Of Course I > double checked that my file is in correct encoding (utf-8) Also using the > web "Invite new Members" function now results in an unicode error. Ideally, providing a translation file should be all you have to do. I'm not sure why the emails are not coming through correctly. Maybe it needs to have a different content transfer encoding? I'm also not sure why the invite new members would generate a unicode error. If you provide a traceback, we may be able to fix it. > Here is an example of an email: > Return-Path: <testliste3@...> > Subject: Subscription confirmation (mail-command:subscribe-member > <<kai@XXX>> [50674187]) > Content-Transfer-Encoding: quoted-printable > Content-Type: text/plain; charset="utf-8" > X-Mailer: MailBoxer > Date: Wed, 04 Mar 2009 22:07:50 +0100 > > Hallo Kai, > > Wir haben eine Bestellungsanfrage für Ihre E-Mail Adresse für die > > So it seem to have a correct charset > > I also wonder how to change the magic subject words "subscribe" and > "unsubscribe" > > Any help or push in the right direction would be welcome. > > Thanks > > Kai I believe that mailboxer has the concept of changing the words subscribe and unsubscribe, but I think that listen has some hard coded regular expressions with the words subscribe/unsubscrbe in it. So I doubt that there will be an easy way for to get this functionality. Unfortunately, I don't think i18n is very high on the priority list for most of us right now that maintain listen, but we'd certainly welcome patches that make listen more i18n friendly. Robert
-
Robert Marianski wrote: > I believe that mailboxer has the concept of changing the words subscribe > and unsubscribe, but I think that listen has some hard coded regular > expressions with the words subscribe/unsubscrbe in it. So I doubt that > there will be an easy way for to get this functionality. > > Unfortunately, I don't think i18n is very high on the priority list for > most of us right now that maintain listen, but we'd certainly welcome > patches that make listen more i18n friendly. and this could change at any time, too... it's not that we don't care about these issues, we very much do, our time is limited and this isn't at the top of our queue ATM. please feel free to open tickets on all such issues in the listen trac instance: http://oss.openplans.org/listen -r
-
On 05/03/2009 11:19, Robert Marianski wrote: > > Unfortunately, I don't think i18n is very high on the priority list for > most of us right now that maintain listen, but we'd certainly welcome > patches that make listen more i18n friendly. > Hi guys Recently i published on Listen SVN Collective my contribution about the i18n with Spanish L10n for the 0.6dev version [0]. Coming soon i wish to add support for the 0.6 branch and also i hope you try and tell me your comments see you around [0] http://svn.plone.org/svn/collective/Products.listen/trunk/Products/listen/ > Robert
-