Now that Launchpad is free software, we should consider whether to
move translations there. While I greatly appreciate Cristobal's
gracious donation of a Pootle server to the project, I'm not sure
we've had much traction with it. I'll regrettably take responsibility
for not helping to push that more.
I am interested in what developers (e.g. Mark) and translators alike
think about such a move, and we have several options. We could move
all translations to LP, only future (read: Mailman 2.2 and/or 3.0)
translations there, or nothing. I don't want to make this decision
alone -- I like to get as much consensus as possible from everyone who
would be affected by the change.
If there are concerns, questions, or complaints about Launchpad's
translation services, feel free to bring that up here or in the
Launchpad public forums. I'll answer as best I can or find an expert
on that part of the system. From my perspective, it would be nice to
re-integrate this part of the development/release cycle.
On Jul 23, 2009, at 2:29 PM, Mikhail Sobolev wrote:
> Please do. I'm certain I sent a message to mailman-i18n quite some
Thanks Misha. We're going to move all translations to Launchpad, so
most of this workflow will change, hopefully for the better. More to
come, when I get a few things set up.
Suppose for example that a list's preferred language is English, but a
particular member's preferred language is Spanish.
If the user goes to http://www.example.com/mailman/options/LIST, the
options login page is displayed in English, and if the user either
logs in or requests unsubscription from that page, she will get an
options page or an unsubscription confirmation in English.
She can first select Spanish as the language for the login page and
redisplay it in Spanish and then it works as expected.
The intent of this is to allow someone who may have accidently (or by
email) subscribed in the list's preferred language to select a
different language for unsubscribing or for the options page.
This may be the desirable behavior, but an alternative is to use the
user's current preferred language for this. Which is better depends on
whether the user's current preferred language is intentional or
accidental which is difficult to know, but if the user's language
choice is accidental, it is likely to be the same as the list's
language anyway, so it seems that setting the language for the options
page or unsubscribe confirmation to the user's preferred language in
the case where the language of the options login page is the list's
language might be a good compromise.
What do people think about this?
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
I'd like to sign up as Champion for a Welsh translation. No
mention of this in the archives, so I don't think I'm treading
on any toes.
Illtud Daniel illtud.daniel(a)llgc.org.uk
Prif Swyddog Technegol Chief Technical Officer
Llyfrgell Genedlaethol Cymru National Library of Wales