From clytie at riverland.net.au  Mon May  3 11:34:10 2010
From: clytie at riverland.net.au (Clytie Siddall)
Date: Mon, 3 May 2010 19:04:10 +0930
Subject: [Mailman-i18n] Fwd:  Mailman finnish translation
References: <4BDE793D.3000506@stonelake.fi>
Message-ID: <AF6D5F22-0149-4E0D-BB46-D93DFF86EBC6@riverland.net.au>

My reply is below. (Reminder: please don't top-post. Quote the important parts of the original message, then reply below the quoted text.)

Begin forwarded message:

> From: Joni T?yryl? <joni.toyryla at stonelake.fi>
> Date: 3 May 2010 4:50:29 PM ACST
> To: Clytie Siddall <clytie at riverland.net.au>
> Subject: Re: [Mailman-i18n] Mailman finnish translation
> 
> Hello Clytie Siddall,
> 
> I have now talked with Pekka Haavisto and he is no longer interested about doing translations. Instead, he asked me to continue with translation work. In first place i would like to to fix errors on translations but i dont know how to start. If you can help me, thanks!
> 
> Best regards,
> Joni
> 
> 
> Clytie Siddall wrote:
>> Tervetuloa Joni :)
>> 
>> (Welcome)
>> 
>> On 16/04/2010, at 6:14 PM, Joni T?yryl? wrote:
>> 
>>  
>>> Hi,
>>> The Finnish translation has some serious errors. I tried to contact the translator but there's no reply. Do you have any ideas on how to correct the translation?
>>>    
>> 
>> According to our list of Mailman Language Champions:
>> 
>> http://wiki.list.org/display/DEV/Languages
>> 
>> the person responsible for our Finnish translation is Piekka Haavisto. Is this the person you tried to contact?
>> 
>> If not, please email Piekka about the errors in translation.
>> 
>> If you have tried to contact Piekka and not had a reply, how long is it since you sent your email?
>> 
>> Thankyou for your interest in Mailman. We will get this sorted out. :)
>> 

Hello again Joni :)

As you can see, I've forwarded your message to the list. This is the best place to discuss these things, so new translators in the future can read about them. (When you click "Reply", check that the To: header contains "mailman-i18n", as some lists default to sender, and that can be confusing and inconvenient.)

If Pekka is no longer interested in translating Mailman, are you willing to be our Finnish Mailman Champion? Please say, so I can change the details in our wiki.

http://wiki.list.org/display/DEV/Languages

To start with, you need to read our Translation Howto:

http://wiki.list.org/display/DEV/i18nhowto

This tells you how to get the Mailman files, and what to do with them.

Once you've read this, please feel free to ask any further questions here. :)

from Clytie 

Vietnamese Free Software Translation Team


From joni.toyryla at stonelake.fi  Mon May  3 11:43:56 2010
From: joni.toyryla at stonelake.fi (=?windows-1258?Q?Joni_T=F6yryl=E4?=)
Date: Mon, 03 May 2010 12:43:56 +0300
Subject: [Mailman-i18n] Fwd:  Mailman finnish translation
In-Reply-To: <AF6D5F22-0149-4E0D-BB46-D93DFF86EBC6@riverland.net.au>
References: <4BDE793D.3000506@stonelake.fi>
	<AF6D5F22-0149-4E0D-BB46-D93DFF86EBC6@riverland.net.au>
Message-ID: <4BDE9ADC.4000406@stonelake.fi>


> Hello again Joni :)
>
> As you can see, I've forwarded your message to the list. This is the best place to discuss these things, so new translators in the future can read about them. (When you click "Reply", check that the To: header contains "mailman-i18n", as some lists default to sender, and that can be confusing and inconvenient.)
>
> If Pekka is no longer interested in translating Mailman, are you willing to be our Finnish Mailman Champion? Please say, so I can change the details in our wiki.
>
> http://wiki.list.org/display/DEV/Languages
>
> To start with, you need to read our Translation Howto:
>
> http://wiki.list.org/display/DEV/i18nhowto
>
> This tells you how to get the Mailman files, and what to do with them.
>
> Once you've read this, please feel free to ask any further questions here. :)
>
> from Clytie 
>   

Hello!

At this time i am willing to fix the errors. My opinion is that name of 
the original author must stay and my work title can be  for example 
"05/2010 - Fixes for original translation by Joni T?yryl?". After i have 
fixed the translation errors i will think about being the Finnish 
translator for other areas. Would this be ok?

Thanks,
Joni





From barry at list.org  Tue May  4 17:33:45 2010
From: barry at list.org (Barry Warsaw)
Date: Tue, 4 May 2010 11:33:45 -0400
Subject: [Mailman-i18n] Logo contest voting is open!
In-Reply-To: <306E1CFE-8F1E-4875-B804-214FD7D5BFFC@riverland.net.au>
References: <20100408174413.06155797@heresy>
	<306E1CFE-8F1E-4875-B804-214FD7D5BFFC@riverland.net.au>
Message-ID: <20100504113345.66abe201@heresy>

Hi Clytie!

On Apr 16, 2010, at 10:31 PM, Clytie Siddall wrote:

>I do have a question or two. ;)

:)

>In voting for the logo, I also consulted my daughter, an embryo graphic
>designer. She asked "What is the logo for? Where will it be displayed? Will
>it also be used as a program icon?" She definitely has a point or three
>there.

Definitely.  Initially, I want to use the logo to re-brand the website and
wiki.  I'd like to use the logo on the relevant Launchpad pages to tie all the
development resources together.  We will use the logo on the default new web
ui pages, and hopefully a scaled down version as a new favicon.  Mailman isn't
a desktop application so I don't see much opportunity to use it as a
traditional desktop program icon.

>It would be useful to have this information on the voting page, e.g. "This
>logo will be displayed on X and Y, and it will (not) be used as a program
>icon."

It would be, but the voting page is pretty limited and I can't do much about
changing it now that the vote is in progress.

>Only one of the logos was suitable for use as an icon, and it was the "M"
>one, which is otherwise quite unsuitable, since it doesn't show Mailman's
>main function: email. One icon was in the form of a badge, which might not
>work well in different display areas. One had a postmark, which is becoming
>increasingly irrelevant in an electronic age.

I'm refraining from stating my preferences, but once we have a winner and the
artwork is assigned to the FSF, we can make (hopefully minor) modifications to
suite the different applications.

>While the "postage stamp" image is still relevant to some extent, the most
>powerful image shown was the "@" symbol, universally associated with email.
>
>I would have loved to see a GNU (horns and all) intertwined with the "@"
>symbol somehow. That would say it all.

Perhaps so, but these are the logos we got as submissions and we're deep into
the contest, so I don't think there's much we can do about that now.  I'm sure
some day we'll have another contest. :)

-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-i18n/attachments/20100504/212bcc78/attachment.pgp>

From joni.toyryla at stonelake.fi  Wed May  5 11:38:41 2010
From: joni.toyryla at stonelake.fi (=?windows-1258?Q?Joni_T=F6yryl=E4?=)
Date: Wed, 05 May 2010 12:38:41 +0300
Subject: [Mailman-i18n] Fwd:  Mailman finnish translation
In-Reply-To: <AF6D5F22-0149-4E0D-BB46-D93DFF86EBC6@riverland.net.au>
References: <4BDE793D.3000506@stonelake.fi>
	<AF6D5F22-0149-4E0D-BB46-D93DFF86EBC6@riverland.net.au>
Message-ID: <4BE13CA1.4010602@stonelake.fi>

Hello!

This is about Finnish translation of Mailman- postlist. I have now fixed 
errors in my local copy. However, i have few questions and remarks. 
Sorry if im posting stupid questions, i rather ask than ignore.

1) At start, thanks for the original translator, it has been lots of 
work and he has done great work! However there were few translation 
errors (rather bad since they occured in admin- indexpage and about 
every page, page header for example). They are fixed. About my skills, 
im not a professional translator but i will do my best :) Im confident 
with python and i think it helps me a bit here.

2) I fixed the errors by searching them from messages.po. Also i fixed 
most of the lines marked as "#,fuzzy". I happily realised that msgfmt 
will inform if translation does not end or start with correct newline 
character (either missing or extra), thats friendly.

3) Question about the Tone of the translation.
In Finnish, i could use normal or more gentle language, which is 
preferred more? At the moment language is normal "mode" but for example 
in error/warning messages its quit harsh for common user. For example:
Native: "You have made a mistake"
Finnish 1: "Teit virheen" (normal)
Finnish 2: "Olette tehneet virheen" (more gentle)
I will use same tone as it has now (normal) but personally i like gentle 
way more.

4) If im not totally sure about the exact meaning of native string i 
will use form "<finnish> (native)". When i know better translation i 
will remove (native) part. This can be also only in my local copy, dunno 
which is better.

5) Natives
-- Is this correct native message? What this actually means? Without 
double "concerning"- word.
#~ msgid "Policies concerning concerning the content of list traffic."

6) White spaces
-- About white spaces, should they be as in native (as close as 
possible) or does it make any difference?
-- How long the line should be, exactly as long in characters as native?
--  For example as in this native:
#: Mailman/Commands/cmd_confirm.py:18
#, fuzzy
msgid ""
"\n"
"    confirm <confirmation-string>\n"
"        Confirm an action.  The confirmation-string is required and 
should "
"be\n"
"        supplied by a mailback confirmation notice.\n"

7) What means stripping here? removing white spaces, removing address or 
domain or what?
#: Mailman/Gui/General.py:163
#, fuzzy
msgid ""
"Should any existing <tt>Reply-To:</tt> header found in the\n"
"             original message be stripped?  If so, this will be done\n"
"             regardless of whether an explict <tt>Reply-To:</tt> header 
is\n"
"             added by Mailman or not."

8) Why i get 158 untranslated messages, as far as i know everything 
should be translated?
:~$ msgfmt -cv -o /dev/null 
/var/lib/mailman/messages/fi/LC_MESSAGES/mailman.po
1192 translated messages, 5 fuzzy translations, 158 untranslated messages.

9) In my local copy i have only en- subfolder in /templates folder. Does 
this mean that finnish translation is missing for all templates?


Thanks!

Best regards,

Joni T?yryl?


From eirbir at gmail.com  Wed May  5 17:25:09 2010
From: eirbir at gmail.com (Eirik U. Birkeland)
Date: Wed, 5 May 2010 17:25:09 +0200
Subject: [Mailman-i18n] Me and Mailman
Message-ID: <z2jeb627fae1005050825r3005c708o268e870b7e49ac1a@mail.gmail.com>

Hi. Reacting to the point ?Please introduce yourself, so we get to
meet you, and to find out what you are going to contribute? I want to
say that my name is Eirik U. Birkeland, and I come from Norway. I have
already (locally) started a Norwegian Nynorsk (nn) translation of
mailman, and am also able to help out with the existing Norwegian
Bokm?l (nb) one. I have been involved with several free software
translation projects during the past 3?4 years or so, among them KDE
and OpenOffice.org.

Now for a few questions/comments I wanted to raise:
1. Can somebody formally start the process of adding Norwegian Nynorsk
(nn) as a language in Mailman?

2. Is there demanded a certain amount of work to have a SVN account? I
have one at several of the other projects I?ve been involved with, so
I?m quite familiar with it, and since there is noone else for
Norwegian Nynorsk, so?

3. With the current information in mailman, it gives me and every
other user the impression that Norwegian Bokm?l (nb) is the only form
of Norwegian (no), as it is called the latter. Please change the name
to Norwegian Bokm?l and the language code to nb.

4. I saw Barry Warsaw write in another email to this list that:
?Ultimately we're going to move all translations to Launchpad, but
probably only for the Mailman 3 series.? I just wanted to say that I
would *strongly* recommend you not to. The list of cons with the
Launchpad translation system is longer than you could possibly
imagine. In Norway we have seen several high-quality translations
being virtually ruined by it. Translating over the Internet is a
*much* slower and more ineffective way of doing it than using an
offline translation software, like e.g. Lokalize or Poedit. Using just
ordinar .po files with a statistics system like the one for KDE [1] is
by far a better solution IMHO.

[1] http://l10n.kde.org/stats/gui/stable-kde4/team/

Best,
Eirik U. Birkeland

From mark at msapiro.net  Sat May  8 02:55:02 2010
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 07 May 2010 17:55:02 -0700
Subject: [Mailman-i18n] Fwd:  Mailman finnish translation
In-Reply-To: <4BE13CA1.4010602@stonelake.fi>
References: <4BDE793D.3000506@stonelake.fi>	<AF6D5F22-0149-4E0D-BB46-D93DFF86EBC6@riverland.net.au>
	<4BE13CA1.4010602@stonelake.fi>
Message-ID: <4BE4B666.8090009@msapiro.net>

On 5/5/2010 2:38 AM, Joni T?yryl? wrote:
> 
> 5) Natives
> -- Is this correct native message? What this actually means? Without
> double "concerning"- word.
> #~ msgid "Policies concerning concerning the content of list traffic."


Messages that begin with #~ are "obsolete message" comments. They are
messages that couldn't be matched against a current message in the
template (.pot) file when msgmerge was run.

This particular message has not been in the source for a long time. The
actual message in the current source is the one immediately following
the line

#: Mailman/Gui/ContentFilter.py:42


> 6) White spaces
> -- About white spaces, should they be as in native (as close as
> possible) or does it make any difference?
> -- How long the line should be, exactly as long in characters as native?
> --  For example as in this native:
> #: Mailman/Commands/cmd_confirm.py:18
> #, fuzzy
> msgid ""
> "\n"
> "    confirm <confirmation-string>\n"
> "        Confirm an action.  The confirmation-string is required and
> should "
> "be\n"
> "        supplied by a mailback confirmation notice.\n"


This particular message goes in the body of an email, so the lines
should be ind3ented, wrapped and filled as necessary to make a uniform
looking email body. In other messages that are ultimately destined for
HTML for example, the line lengths are not important.


> 7) What means stripping here? removing white spaces, removing address or
> domain or what?
> #: Mailman/Gui/General.py:163
> #, fuzzy
> msgid ""
> "Should any existing <tt>Reply-To:</tt> header found in the\n"
> "             original message be stripped?  If so, this will be done\n"
> "             regardless of whether an explict <tt>Reply-To:</tt> header
> is\n"
> "             added by Mailman or not."


Stripping here means removal of the entire Reply-To: header from the
incoming mail. In this context, you could replace "stripped" with
"removed" without changing the meaning.


> 8) Why i get 158 untranslated messages, as far as i know everything
> should be translated?
> :~$ msgfmt -cv -o /dev/null
> /var/lib/mailman/messages/fi/LC_MESSAGES/mailman.po
> 1192 translated messages, 5 fuzzy translations, 158 untranslated messages.


There are 158 messages where msgstr is empty.


> 9) In my local copy i have only en- subfolder in /templates folder. Does
> this mean that finnish translation is missing for all templates?


Are you looking at the Mailman 3.0 branch? If so, the templates are in
the message catalog and are installed for selected languages at
installation time. But, you should be looking at the 2.1 branch because
that has the most complete and up to date translations at this time. In
the 2.1 distribution, the templates are in the templates directory in
the distribution.

Finally, note there is a bin/transcheck script that checks for the
presence of all the appropriate substitution variables.

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


From david.planella at googlemail.com  Sat May  8 12:04:27 2010
From: david.planella at googlemail.com (David Planella)
Date: Sat, 8 May 2010 12:04:27 +0200
Subject: [Mailman-i18n] Me and Mailman
In-Reply-To: <z2jeb627fae1005050825r3005c708o268e870b7e49ac1a@mail.gmail.com>
References: <z2jeb627fae1005050825r3005c708o268e870b7e49ac1a@mail.gmail.com>
Message-ID: <AANLkTilfUU830r7v_eztlalmLylvw80djhhCGYL4AMsX@mail.gmail.com>

Hi Eirik,

I'll answer the bits I can and I'll leave the rest to others more
knowledgeable on the other questions.

2010/5/5 Eirik U. Birkeland <eirbir at gmail.com>:
> Hi. Reacting to the point ?Please introduce yourself, so we get to
> meet you, and to find out what you are going to contribute? I want to
> say that my name is Eirik U. Birkeland, and I come from Norway. I have
> already (locally) started a Norwegian Nynorsk (nn) translation of
> mailman, and am also able to help out with the existing Norwegian
> Bokm?l (nb) one. I have been involved with several free software
> translation projects during the past 3?4 years or so, among them KDE
> and OpenOffice.org.
>
> Now for a few questions/comments I wanted to raise:
> 1. Can somebody formally start the process of adding Norwegian Nynorsk
> (nn) as a language in Mailman?
>

You'll find more info on the process here:

  http://wiki.list.org/display/DEV/Internationalization

You've already done the first step in introducing yourself on the list
:), and I think now the next one is to sign the disclaimer assigning
the copyright to the FSF, so that they can maintain it and your
translation can be used in Maillman.

You'll find more info here (that's also explained in the wiki page above):

  http://translationproject.org/html/whydisclaim.html

If I've forgotten any step, I'm sure Barry, Mark or others on the list
will chip in.

> 2. Is there demanded a certain amount of work to have a SVN account? I
> have one at several of the other projects I?ve been involved with, so
> I?m quite familiar with it, and since there is noone else for
> Norwegian Nynorsk, so?
>
> 3. With the current information in mailman, it gives me and every
> other user the impression that Norwegian Bokm?l (nb) is the only form
> of Norwegian (no), as it is called the latter. Please change the name
> to Norwegian Bokm?l and the language code to nb.
>
> 4. I saw Barry Warsaw write in another email to this list that:
> ?Ultimately we're going to move all translations to Launchpad, but
> probably only for the Mailman 3 series.? I just wanted to say that I
> would *strongly* recommend you not to. The list of cons with the
> Launchpad translation system is longer than you could possibly
> imagine.

If the list of cons is so long, I'd like to ask you to share them on
the list, so they can be evaluated. I can only see pros, but then
again, I'm a bit biased, being a long time user of Launchpad
Translations, but also of many other systems, such as the GNOME
Translation Project, Pootle, the Translation Project, the several
methods Debian use, and also many projects in which PO files are
simply sent on a mailing list and committed on a repo.

I think having a translation management system (just any!) for an Open
Source project, as opposed to having to fetch PO files from a repo and
sending them to the list is a big improvement for both translators and
developers, and it just speaks for the maturity of a project. Here are
my general pros:

* Translators can work almost independently from developers
* Less work for developers and maintainers
* Less technical skills involved for translation, lower entry barrier
for contributors

I find last one the most important one. While some people will argue
that making the entry barrier for translation will result in higher
quality translations (I've heard that many times), I'm of the opinion
that artificially raising the entry barrier always results in less
contributions, regardless of the quality. Quality in translation can
only be achieved by established review practices in the translation
teams, and that is independent of the translation tool being used.
Having an advanced translation management tool plus using QA practices
can only bring advantages.

As for the pros specific to Launchpad Translations:

* As Mailman is already using bzr for development, the bzr integration
with translations can be taken advantage of. This includes:
** Automatic translation imports: translations are imported
automatically from a given code branch
** Automatic translation exports: translations are exported daily
(read automatically committed to a branch of choice) when translators
do their work
* The translation of several project versions can be maintained from
the same central location.
* Translations are shared between the several different project
versions. That means that translators don't have to complete
translations in all versions or fix typos or spelling mistakes over
and over: translate in one series (version) and your changes will be
propagated instantly to the identical messages in all other series.
You can also choose identical messages to diverge between series.
* A simple, clean UI that is easy to use for new and experienced contributors
* Compatibility with traditional translation methods: if you prefer
translating offline, you can simply download a PO file, translate it
with your favourite editor, and upload it again. You don't need access
to any repo or need to depend on someone else to upload it for you.
* Statistics are shown in the UI to better track your work as a
translator and help setting goals.
* Different permission levels: as Mailman requires you as a translator
to have signed the disclaimer, only those people who've done that will
be able to translate it. Launchpad supports this as one of its several
permission policies, which is the one recommended for most projects
anyway. I myself find that an Open translation policy, without any
kind of peer review, be it in Launchpad or in any other project, does
often lead to lesser quality translations.
* Basic review capabilities: you can mark a string as "Needs review"
and save it, and it will be stored as suggestion, but not submitted
until someone else explicitly reviews it and accepts it (or provides
another suggestion).
* Global suggestions from all projects translated in Launchpad. While
not functioning as a proper translation memory, this is quite powerful
in terms of using the work of the huge pool of translators in
Launchpad. Quite often translating is only a matter of reviewing,
pointing and clicking.

> In Norway we have seen several high-quality translations
> being virtually ruined by it.

That is related to the permissions chosen by each particular project.
Launchpad offers several translation permission levels, from very open
to very restrictive [1], and it's up to the project maintainers to
choose.

I do agree that choosing Open permissions is not the best option, and
often what translators do is to ask developers to choose a more
restrictive permission assigned to a set of language teams, who are
ultimately responsible for translations in their own language.

For the record though, when using Open permissions, what I've seen is
more wrong translations or with typos being submitted, rather than
overwriting current ones.

> Translating over the Internet is a
> *much* slower and more ineffective way of doing it than using an
> offline translation software, like e.g. Lokalize or Poedit.

As mentioned above, you can do exactly this with Launchpad
Translations, you just download the PO file, translate it offline with
an editor, and upload it again.

> Using just
> ordinar .po files with a statistics system like the one for KDE [1] is
> by far a better solution IMHO.
>
> [1] http://l10n.kde.org/stats/gui/stable-kde4/team/
>
> Best,
> Eirik U. Birkeland

I won't argue now on what system is best (other might find Vertimus in
GNOME better, other Scripty and stats in KDE better, other the stats
for Mozilla projects better). I do believe though, that any online
translation system (be it Launchpad, Pootle, Narro, etc.) can only
ease the work of translators, which for me is the ultimate goal in
making the process of providing better natural language support to
applications easy.

Cheers,
David.

[1] https://help.launchpad.net/Translations/YourProject/PermissionPolicies

From mark at msapiro.net  Mon May 10 21:26:50 2010
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 10 May 2010 12:26:50 -0700
Subject: [Mailman-i18n] Me and Mailman
In-Reply-To: <AANLkTilfUU830r7v_eztlalmLylvw80djhhCGYL4AMsX@mail.gmail.com>
References: <z2jeb627fae1005050825r3005c708o268e870b7e49ac1a@mail.gmail.com>
	<AANLkTilfUU830r7v_eztlalmLylvw80djhhCGYL4AMsX@mail.gmail.com>
Message-ID: <4BE85DFA.6020205@msapiro.net>

On 5/8/2010 3:04 AM, David Planella wrote
> 
> If I've forgotten any step, I'm sure Barry, Mark or others on the list
> will chip in.


Thanks David. Just to add one more point.


>> 2. Is there demanded a certain amount of work to have a SVN account? I
>> have one at several of the other projects I?ve been involved with, so
>> I?m quite familiar with it, and since there is noone else for
>> Norwegian Nynorsk, so?


We no longer use the SVN repository on SourceForge. It is out of date.
We use Bazaar on Launchpad. Current branches are at
<https://code.launchpad.net/mailman>. You can register your own branch
there and push your code to it and when it's ready, create a merge proposal.

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


From barry at list.org  Wed May 12 22:45:38 2010
From: barry at list.org (Barry Warsaw)
Date: Wed, 12 May 2010 22:45:38 +0200
Subject: [Mailman-i18n] Translating on Launchpad (was Re:  Me and Mailman)
In-Reply-To: <AANLkTilfUU830r7v_eztlalmLylvw80djhhCGYL4AMsX@mail.gmail.com>
References: <z2jeb627fae1005050825r3005c708o268e870b7e49ac1a@mail.gmail.com>
	<AANLkTilfUU830r7v_eztlalmLylvw80djhhCGYL4AMsX@mail.gmail.com>
Message-ID: <20100512224538.30305e6e@heresy>

On May 08, 2010, at 12:04 PM, David Planella wrote:

>I'll answer the bits I can and I'll leave the rest to others more
>knowledgeable on the other questions.

Thanks very much for following up David (and Mark for the clarification on
Bazaar).  This is a great segue for yet another discussion on moving all
translations to Launchpad.

We're definitely going to translate MM3 in Launchpad.  David was kind enough
to help me today with some administrative tasks in setting up our translations
on Launchpad.  While I've done so before, I want to once again propose that we
move MM 2.1 translations to Launchpad as well.  Mark can veto this decision,
but barring that unless there's widespread revolt, I'd strongly like to do it.

Read David's full post for a list of the benefits that we will gain.  For me,
the ability to import .pot and .po files from a branch, and more importantly
export them to a branch, is very compelling from a maintainer's point of
view.  We can either have Launchpad commit changes to the development branches
directly, or as I think would be better, to use a separate branch and have one
of us do occasional merges to the series trunk.  This really reduces the
burden of getting updated translations, and leverages more of the tools we're
already using (i.e. Bazaar).  I also think it will help recruit more
translators, while still maintaining our strict legal requirements.

I also think that those of you who are currently translating do not really
need to change your workflow much, if you don't want to use the LP ui.  You
can still grab the .po file, do your updates in your favorite local tool, and
then you would upload them to LP.  The only thing this change would require
would be a Launchpad account, and I hope that with LP being free software,
that will not be too high of a hurdle.

Current translators, please provide feedback.  I will do my best to find
answers to any concerns, but of course David is much more knowledgeable in
this area than I am and he is here to help too.  I'm setting up some branches
now for the 2.1 translation so I'm hoping that at least some of the
translation teams will be interested in giving this a try.

Cheers,
-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-i18n/attachments/20100512/0793c1fa/attachment.pgp>