From genghiskhan at gmx.ca  Fri May  2 07:22:02 2014
From: genghiskhan at gmx.ca (Genghis Khan)
Date: Fri, 02 May 2014 01:22:02 -0400
Subject: [Mailman-i18n] Hebrew translation
Message-ID: <20140502052203.236310@gmx.com>

Hallo,

I would like to be joined to GNU Mailman translators translation
group[0] to gain privileges to update Hebrew translation for GNU
Mailman. ?My Launchpad Id is ~genghiskhan[1]

[0] https://translations.launchpad.net/+groups/mailman-translators
[1] https://launchpad.net/~genghiskhan

Regards,
--GK

-- 
() ?ascii ribbon campaign - against html e-mail
/\ ?www.asciiribbon.org ? - against proprietary attachments

From mark at msapiro.net  Fri May  2 08:02:45 2014
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 01 May 2014 23:02:45 -0700
Subject: [Mailman-i18n] Hebrew translation
In-Reply-To: <20140502052203.236310@gmx.com>
References: <20140502052203.236310@gmx.com>
Message-ID: <53633505.30808@msapiro.net>

On 05/01/2014 10:22 PM, Genghis Khan wrote:
> Hallo,
> 
> I would like to be joined to GNU Mailman translators translation
> group[0] to gain privileges to update Hebrew translation for GNU
> Mailman.  My Launchpad Id is ~genghiskhan[1]
> 
> [0] https://translations.launchpad.net/+groups/mailman-translators
> [1] https://launchpad.net/~genghiskhan


That group never got off the ground and was primarily aimed at Mailman 3
in any case.

Are you interested in Mailman 2.1 or Mailman 3? If 2.1, I suggest you
wait a day or two because there is a significant change to one specific
string that is not yet in the mailman.pot template or msgmerged into
messages/he/LC_MESSAGES/mailman.po. In any case, translating does not
depend on any membership in the translation group. See the detailed
procedure at <http://wiki.list.org/display/DEV/i18nhowto>.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Sat May  3 20:30:36 2014
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 03 May 2014 11:30:36 -0700
Subject: [Mailman-i18n] Mailman 2.1.18 final release
Message-ID: <536535CC.9080908@msapiro.net>

I'm pleased to announce the final release for Mailman 2.1.18.

This release has new features to help with mitigation of the impacts of
DMARC on mailing lists as well as fixing several bugs.

Python 2.4 is the minimum supported, but Python 2.7 is recommended.

There are significant new i18n strings associated with the DMARC
mitigation features. If you are interested in helping with the
translations of these strings, see <http://wiki.list.org/x/MQ>.

There is also a new dependency associated with these features. Namely,
the new Privacy options -> Sender filters -> dmarc_moderation_action
feature requires that the dnspython <http://www.dnspython.org/> package
be available in Python.

See the attached README for more details.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see:

http://www.list.org
http://www.gnu.org/software/mailman
http://mailman.sourceforge.net/

Mailman 2.1.18 can be downloaded from

https://launchpad.net/mailman/2.1/
http://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
-------------- next part --------------
2.1.18 (03-May-2014)

  Dependencies

    - There is a new dependency associated with the new Privacy options ->
      Sender filters -> dmarc_moderation_action feature discussed below.
      This requires that the dnspython <http://www.dnspython.org/> package
      be available in Python.  This package can be downloaded from the above
      site or from the CheeseShop <https://pypi.python.org/pypi/dnspython/>
      or installed with pip.

  New Features

    - The from_is_list feature introduced in 2.1.16 is now unconditionally
      available to list owners.  There is also, a new Privacy options ->
      Sender filters -> dmarc_moderation_action feature which applies to list
      messages where the From: address is in a domain which publishes a DMARC
      policy of reject or possibly quarantine.  This is a list setting with
      values of Accept, Wrap Message, Munge From, Reject or Discard. There is
      a new DEFAULT_DMARC_MODERATION_ACTION configuration setting to set the
      default for this, and the list admin UI is not able to set an action
      which is 'less' than the default.  The prior ALLOW_FROM_IS_LIST setting
      has been removed and is effectively always Yes. There is a new
      dmarc_quarantine_moderation_action list setting with default set by a
      new DEFAULT_DMARC_QUARANTINE_MODERATION_ACTION configuration setting
      which in turn defaults to Yes.  The list setting can be set to No to
      exclude domains with DMARC policy of quarantine from
      dmarc_moderation_action.

      dmarc_moderation_action and from_is_list interact in the following way.
      If the message is From: a domain to which dmarc_moderation_action applies
      and if dmarc_moderation_action is other than Accept,
      dmarc_moderation_action applies to that message.  Otherwise the
      from_is_list action applies.

      Also associated with dmarc_moderation_action are configuration settings
      DMARC_RESOLVER_TIMEOUT and DMARC_RESOLVER_LIFETIME. These are described
      in more detail in Defaults.py.  There are also new vette log entries
      written when dmarc_moderation_action is found to apply to a post.

  i18n

    - Added missing <mm-digest-question-start> tag to French listinfo template.
      (LP: #1275964)

  Bug Fixes and other patches

    - Removed HTML tags from the title of a couple of rmlist.py pages because
      browsers don't render tags in the title.  (LP: #265848)

    - Most Mailman generated notices to list owners and moderators are now
      sent as Precedence: list instead of bulk.  (LP: #1313146)

    - The Reply-To: munging options weren't honored if there was no
      from_is_list action.  (LP: #1313010)

    - Changed from_is_list actions to insert the list address in Cc: if the
      list is fully personalized.  Otherwise, the list address is only in
      From: and Reply-To: overrides it.  (LP: #1312970)

    - Fixed the Munge From action to only Munge the From: and/or Reply-To: in
      the outgoing message and not in archives, digests and messages sent via
      the usenet gateway.  (LP: #1311431)

    - Fixed a long standing issue in which a notice sent to a user whose
      language is other than that of the list can cause subsequent things
      which should be in the list's language to be in the user's language
      instead.  (LP: #1308655)

    - Fixed the admin Membership List so a search string if any is not lost
      when visiting subsequent fragments of a chunked list.  (LP: #1307454)

    - For from_is_list feature, use email address from original From: if
      original From: has no display name and strip domain part from resultant
      names that look like email addresses.  (LP: #1304511)

    - Added the list name to the vette log "held message approved" entry.
      (LP: 1295875)

    - Added the CGI module name to various "No such list" error log entries.
      (LP: 1295875)

    - Modified contrib/mmdsr to report module name if present in "No such list
      error log entries.

    - Fixed a NameError exception in cron/nightly_gzip when it tries to print
      the usage message.  (LP: #1291038)

    - Fixed a bug in ListAdmin._handlepost that would crash when trying to
      preserve a held message for the site admin if HOLD_MESSAGES_AS_PICKLES
      is False.  (LP: #1282365)

    - The from_is_list header munging feature introduced in Mailman 2.1.16 is
      no longer erroneously applied to Mailman generated notices.
      (LP: #1279667)

    - Changed the message from the confirm CGI to not indicate approval is
      required for an acceptance of an invitation.  (LP: #1277744)

    - Fixed POSTFIX_STYLE_VIRTUAL_DOMAINS to be case-insensitiive.
      (LP: #1267003)

    - Added recognition for another simple warning to bounce processing.
      (LP: #1263247)

    - Fixed a few failing tests in tests/test_handlers.py.  (LP: #1262950)

    - Fixed bin/arch to not create scrubbed attachments for messages skipped
      when processing the --start= option.  (LP: #1260883)

    - Fixed email address validation to do a bit better in obscure cases.
      (LP: #1258703)

    - Fixed a bug which caused some authentication cookies to expire too soon
      if AUTHENTICATION_COOKIE_LIFETIME is non-zero.  (LP: #1257112)
 
    - Fixed a possible TypeError in bin/sync_members introduced in 2.1.17.
      (LP: #1243343)

  Miscellaneous

    - Added to the contrib directory, a script from Alain Williams to count
      posts in a list's archive.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-i18n/attachments/20140503/fddbe41e/attachment.sig>

From genghiskhan at gmx.ca  Sun May  4 18:31:35 2014
From: genghiskhan at gmx.ca (Genghis Khan)
Date: Sun, 04 May 2014 18:31:35 +0200
Subject: [Mailman-i18n] Hebrew translation
References: <20140502052203.236310@gmx.com>	<53633505.30808@msapiro.net>
Message-ID: <20140504163136.70860@gmx.com>

On Thu, 01 May 2014 23:02:45 -0700
Mark Sapiro <mark at msapiro.net> wrote:

> On 05/01/2014 10:22 PM, Genghis Khan wrote:
> > Hallo,
> > 
> > I would like to be joined to GNU Mailman translators translation
> > group[0] to gain privileges to update Hebrew translation for GNU
> > Mailman. My Launchpad Id is ~genghiskhan[1]
> > 
> > [0] https://translations.launchpad.net/+groups/mailman-translators
> > [1] https://launchpad.net/~genghiskhan
> 
> 
> That group never got off the ground and was primarily aimed at
> Mailman 3 in any case.
> 
> Are you interested in Mailman 2.1 or Mailman 3?

Whichever one you would want me to translate.

> If 2.1, I suggest you wait a day or two because there is a
> significant change to one specific string that is not yet in the
> mailman.pot template or msgmerged into
> messages/he/LC_MESSAGES/mailman.po. In any case, translating does not
> depend on any membership in the translation group. See the detailed
> procedure at <http://wiki.list.org/display/DEV/i18nhowto>.
> 

Thank you for this information and reference.

Since I do not know how to create a Bazaar branch, I think, I will send
an update to this list or to one of the staff members.


P.S. If you are a Hebrew speaker and you are reading this message,
 ? ? please contact me for further collaboration on this matter.

P.S. Is Mr. Dov Zamir, who is the original author of the Hebrew
 ? ? translation, is still active in GNU Mailman?

-- 
() ?ascii ribbon campaign - against html e-mail
/\ ?www.asciiribbon.org ? - against proprietary attachments

From mark at msapiro.net  Tue May  6 05:01:24 2014
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 05 May 2014 20:01:24 -0700
Subject: [Mailman-i18n] Hebrew translation
In-Reply-To: <20140504163136.70860@gmx.com>
References: <20140502052203.236310@gmx.com>	<53633505.30808@msapiro.net>
 <20140504163136.70860@gmx.com>
Message-ID: <53685084.1010605@msapiro.net>

On 05/04/2014 09:31 AM, Genghis Khan wrote:
> On Thu, 01 May 2014 23:02:45 -0700
> Mark Sapiro <mark at msapiro.net> wrote:
> 
>>
>> Are you interested in Mailman 2.1 or Mailman 3?
> 
> Whichever one you would want me to translate.


i18n for Mailman 3 is still not really underway.

Mailman 2.1.18 has just been released with several new strings, so your
help with that would be great.


...
> Since I do not know how to create a Bazaar branch, I think, I will send
> an update to this list or to one of the staff members.


You can send it directly to me. You can download the latest
mailman-2.1.18.tgz from <https://launchpad.net/mailman/2.1/2.1.18>. It
contains the Hebrew message catalog in
messages/he/LC_MESSAGES/mailman.po and templates in templates/he/*.


> P.S. If you are a Hebrew speaker and you are reading this message,
>      please contact me for further collaboration on this matter.


I'm not, but hopefully others on this list are.


> P.S. Is Mr. Dov Zamir, who is the original author of the Hebrew
>      translation, is still active in GNU Mailman?


I don't think I've heard from him since he submitted his original
translation work about 7 years ago.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Tue May  6 08:11:38 2014
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 05 May 2014 23:11:38 -0700
Subject: [Mailman-i18n] Mailman 2.1.18 final release
In-Reply-To: <536535CC.9080908@msapiro.net>
References: <536535CC.9080908@msapiro.net>
Message-ID: <53687D1A.5030302@msapiro.net>

On 05/03/2014 11:30 AM, Mark Sapiro wrote:
> I'm pleased to announce the final release for Mailman 2.1.18.


It appears that the from_is_list and dmarc_moderation_actions Wrap
Message actions may run afoul of this issue
<http://bugs.python.org/issue7970> in the Python email library in
versions older than 2.6.x where x is some number < 5. I.e. I know the
bug is fixed in Python 2.7 and 2.6.5 and not in any 2.5.x or older. I'm
not sure about 2.6.1 - 2.6.4.

I have attached a patch to Mailman/Message.py which I think will fix
this issue if you have it. You will know if you do because all outgoing
mail will be shunted with the exception "TypeError: Expected list, got
<type 'str'>" when SMTPDirect.py invokes the as_string() method on the
message object.

I think this will only occur with those older Pythons and when a Wrap
Message action is applied.

As soon as I get confirmation from the original reporter that the patch
solves the problem, I will release a fixed version.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
-------------- next part --------------
--- /var/MM/2.1/Mailman/Message.py	2014-04-26 21:29:42.282766984 -0700
+++ /var/MM/21/Mailman/Message.py	2014-05-05 22:40:32.412348756 -0700
@@ -59,6 +59,25 @@
         return self.__class__(fp, self._mangle_from_,
                 self.__children_maxheaderlen, self.__children_maxheaderlen)
 
+    # This is the _handle_message method with the fix for bug 7970.
+    def _handle_message(self, msg):
+        s = StringIO()
+        g = self.clone(s)
+        # The payload of a message/rfc822 part should be a multipart sequence
+        # of length 1.  The zeroth element of the list should be the Message
+        # object for the subpart.  Extract that object, stringify it, and
+        # write it out.
+        # Except, it turns out, when it's a string instead, which happens when
+        # and only when HeaderParser is used on a message of mime type
+        # message/rfc822.  Such messages are generated by, for example,
+        # Groupwise when forwarding unadorned messages.  (Issue 7970.)  So
+        # in that case we just emit the string body.
+        payload = msg.get_payload()
+        if isinstance(payload, list):
+            g.flatten(msg.get_payload(0), unixfrom=False)
+            payload = s.getvalue()
+        self._fp.write(payload)
+
 
 

 class Message(email.Message.Message):
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-i18n/attachments/20140505/130222ae/attachment.sig>

From mark at msapiro.net  Tue May  6 19:37:58 2014
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 06 May 2014 10:37:58 -0700
Subject: [Mailman-i18n] Mailman 2.1.18 final release
Message-ID: <53691DF6.1040101@msapiro.net>

A critical incompatibility between the Mailman 2.1.18 final release and
Python versions older than 2.6.5 or thereabouts affecting the DMARC Wrap
Message action was discovered and fixed. This incompatibility also
existed in the 2.1.16 and 2.1.17 releases.

Thus, I have released Mailman 2.1.18-1 with a fix for this
incompatibility. Please use 2.1.18-1 and not 2.1.18.

These releases have new features to help with mitigation of the impacts
of DMARC on mailing lists as well as fixing several bugs.

Python 2.4 is the minimum supported, but Python 2.7 is recommended.

There are significant new i18n strings associated with the DMARC
mitigation features. If you are interested in helping with the
translations of these strings, see <http://wiki.list.org/x/MQ>.

There is also a new dependency associated with these features. Namely,
the new Privacy options -> Sender filters -> dmarc_moderation_action
feature requires that the dnspython <http://www.dnspython.org/> package
be available in Python.

See the attached README for more details.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see:

http://www.list.org
http://www.gnu.org/software/mailman
http://mailman.sourceforge.net/

Mailman 2.1.18-1 can be downloaded from

https://launchpad.net/mailman/2.1/
http://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
2.1.18-1 (06-May-2014)

  Bug fixes and other patches

    - A critical incompatibility between the DMARC Wrap Message action and
      Python versions older than 2.6.x for some x <= 5 existed and caused
      Wrapped message to be shunted.  This is fixed.  (LP: #1316682)

    - Sender: headers are no longer removed in from_is_list Munge From
      actions.  (LP: #1315970)

2.1.18 (03-May-2014)

  Acknowledgements

    - Thanks to Jim Popovitch and Phil Pennock for the branch that formed the
      basis of the dmarc_moderation_action feature.

    - Thanks to Franck Martin et al for the branch that formed the basis of
      the from_is_list feature.

  Dependencies

    - There is a new dependency associated with the new Privacy options ->
      Sender filters -> dmarc_moderation_action feature discussed below.
      This requires that the dnspython <http://www.dnspython.org/> package
      be available in Python.  This package can be downloaded from the above
      site or from the CheeseShop <https://pypi.python.org/pypi/dnspython/>
      or installed with pip.

  New Features

    - The from_is_list feature introduced in 2.1.16 is now unconditionally
      available to list owners.  There is also, a new Privacy options ->
      Sender filters -> dmarc_moderation_action feature which applies to list
      messages where the From: address is in a domain which publishes a DMARC
      policy of reject or possibly quarantine.  This is a list setting with
      values of Accept, Wrap Message, Munge From, Reject or Discard. There is
      a new DEFAULT_DMARC_MODERATION_ACTION configuration setting to set the
      default for this, and the list admin UI is not able to set an action
      which is 'less' than the default.  The prior ALLOW_FROM_IS_LIST setting
      has been removed and is effectively always Yes. There is a new
      dmarc_quarantine_moderation_action list setting with default set by a
      new DEFAULT_DMARC_QUARANTINE_MODERATION_ACTION configuration setting
      which in turn defaults to Yes.  The list setting can be set to No to
      exclude domains with DMARC policy of quarantine from
      dmarc_moderation_action.

      dmarc_moderation_action and from_is_list interact in the following way.
      If the message is From: a domain to which dmarc_moderation_action applies
      and if dmarc_moderation_action is other than Accept,
      dmarc_moderation_action applies to that message.  Otherwise the
      from_is_list action applies.

      Also associated with dmarc_moderation_action are configuration settings
      DMARC_RESOLVER_TIMEOUT and DMARC_RESOLVER_LIFETIME. These are described
      in more detail in Defaults.py.  There are also new vette log entries
      written when dmarc_moderation_action is found to apply to a post.

  i18n

    - Added missing <mm-digest-question-start> tag to French listinfo template.
      (LP: #1275964)

  Bug Fixes and other patches

    - Removed HTML tags from the title of a couple of rmlist.py pages because
      browsers don't render tags in the title.  (LP: #265848)

    - Most Mailman generated notices to list owners and moderators are now
      sent as Precedence: list instead of bulk.  (LP: #1313146)

    - The Reply-To: munging options weren't honored if there was no
      from_is_list action.  (LP: #1313010)

    - Changed from_is_list actions to insert the list address in Cc: if the
      list is fully personalized.  Otherwise, the list address is only in
      From: and Reply-To: overrides it.  (LP: #1312970)

    - Fixed the Munge From action to only Munge the From: and/or Reply-To: in
      the outgoing message and not in archives, digests and messages sent via
      the usenet gateway.  (LP: #1311431)

    - Fixed a long standing issue in which a notice sent to a user whose
      language is other than that of the list can cause subsequent things
      which should be in the list's language to be in the user's language
      instead.  (LP: #1308655)

    - Fixed the admin Membership List so a search string if any is not lost
      when visiting subsequent fragments of a chunked list.  (LP: #1307454)

    - For from_is_list feature, use email address from original From: if
      original From: has no display name and strip domain part from resultant
      names that look like email addresses.  (LP: #1304511)

    - Added the list name to the vette log "held message approved" entry.
      (LP: 1295875)

    - Added the CGI module name to various "No such list" error log entries.
      (LP: 1295875)

    - Modified contrib/mmdsr to report module name if present in "No such list
      error log entries.

    - Fixed a NameError exception in cron/nightly_gzip when it tries to print
      the usage message.  (LP: #1291038)

    - Fixed a bug in ListAdmin._handlepost that would crash when trying to
      preserve a held message for the site admin if HOLD_MESSAGES_AS_PICKLES
      is False.  (LP: #1282365)

    - The from_is_list header munging feature introduced in Mailman 2.1.16 is
      no longer erroneously applied to Mailman generated notices.
      (LP: #1279667)

    - Changed the message from the confirm CGI to not indicate approval is
      required for an acceptance of an invitation.  (LP: #1277744)

    - Fixed POSTFIX_STYLE_VIRTUAL_DOMAINS to be case-insensitiive.
      (LP: #1267003)

    - Added recognition for another simple warning to bounce processing.
      (LP: #1263247)

    - Fixed a few failing tests in tests/test_handlers.py.  (LP: #1262950)

    - Fixed bin/arch to not create scrubbed attachments for messages skipped
      when processing the --start= option.  (LP: #1260883)

    - Fixed email address validation to do a bit better in obscure cases.
      (LP: #1258703)

    - Fixed a bug which caused some authentication cookies to expire too soon
      if AUTHENTICATION_COOKIE_LIFETIME is non-zero.  (LP: #1257112)

    - Fixed a possible TypeError in bin/sync_members introduced in 2.1.17.
      (LP: #1243343)

  Miscellaneous

    - Added to the contrib directory, a script from Alain Williams to count
      posts in a list's archive.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-i18n/attachments/20140506/1e4118d3/attachment.sig>

From dov at zamirfamily.com  Tue May  6 16:33:25 2014
From: dov at zamirfamily.com (=?utf-8?Q?Dov_Zamir?=)
Date: Tue, 6 May 2014 17:33:25 +0300
Subject: [Mailman-i18n] [Virus?] Re:  Hebrew translation
In-Reply-To: <53685084.1010605@msapiro.net>
References: <53685084.1010605@msapiro.net>
Message-ID: <zarafa.5368f2b5.42ea.0493d4fa2ae866e1@mail.zamirfamily.com>

Hi all,

?
Yes, I am still here, however I have not used mailman for many years and was under the impresion that there was very little interest in the Hebrew translation.

I have only ever received one querry concerning it which concerned using Hebrw in the message body and the interface.

?
Since I am no longer on the ml, if you would like to contact me further, please cc me at: linux at zamirfamily dot com

--------------------------------
Dov Zamir

Communications Systems Engineer

email: dov at zamirfamily.com

tel: 972-8-9915499

fax: 972-8-9915274

cell: 972-52-3356642

?

?
-----????? ??????-----
???:Mark Sapiro <mark at msapiro.net>
????:??? 06-05-2014 06:01
????:[Virus?] Re: [Mailman-i18n] Hebrew translation
??:Genghis Khan <genghiskhan at gmx.ca>; mailman-i18n at python.org; 
????:linux <linux at zamirfamily.com>; 
On 05/04/2014 09:31 AM, Genghis Khan wrote:
> On Thu, 01 May 2014 23:02:45 -0700
> Mark Sapiro <mark at msapiro.net> wrote:
> 
>>
>> Are you interested in Mailman 2.1 or Mailman 3?
> 
> Whichever one you would want me to translate.

i18n for Mailman 3 is still not really underway.

Mailman 2.1.18 has just been released with several new strings, so your
help with that would be great.

...
> Since I do not know how to create a Bazaar branch, I think, I will send
> an update to this list or to one of the staff members.

You can send it directly to me. You can download the latest
mailman-2.1.18.tgz from <https://launchpad.net/mailman/2.1/2.1.18>. It
contains the Hebrew message catalog in
messages/he/LC_MESSAGES/mailman.po and templates in templates/he/*.

> P.S. If you are a Hebrew speaker and you are reading this message,
>????? please contact me for further collaboration on this matter.

I'm not, but hopefully others on this list are.

> P.S. Is Mr. Dov Zamir, who is the original author of the Hebrew
>????? translation, is still active in GNU Mailman?

I don't think I've heard from him since he submitted his original
translation work about 7 years ago.

-- 
Mark Sapiro <mark at msapiro.net>??????? The highway is for gamblers,
San Francisco Bay Area, California??? better use your sense - B. Dylan

!DSPAM:1006,5368508d280508149389508!


 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/mailman-i18n/attachments/20140506/cc51a223/attachment.html>

From mcicogni at libero.it  Sat May 17 14:44:25 2014
From: mcicogni at libero.it (Mauro Cicognini)
Date: Fri, 17 May 2014 12:44:25 +0000
Subject: [Mailman-i18n] Mauro Cicognini
Message-ID: <79A1CBD448D30D6A002EEECA2C011890@2get.jp>

http://callwithjoshanddean.com/xkjnueua/oditnrgttiov.bdiwhwjlecmdhudhrgxxjkpytf
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: <http://mail.python.org/pipermail/mailman-i18n/attachments/20140517/56cd9f70/attachment.html>