Mailman-i18n August 2012

Download

mailman-i18n@python.org

3 participants
2 discussions

Re: [Mailman-i18n] [Mailman-Developers] translation of mail templates
by Federico Leva (Nemo) 27 Aug '12

27 Aug '12

Christopher Meng, 27/08/2012 12:03: > Hi. > > What about transifex? I've never used it, but a developer and translator for an OpenStreetMap piece of software recently said: «We ended up with Transifex, which might look cooler but certainly is an inferior tool for the translator I can say now after having used for some hours». <https://translatewiki.net/wiki/Thread:Support/Request_for_comment_on_feasab…> Nemo

1 0

Re: [Mailman-i18n] [Mailman-Developers] translation of mail templates
by Barry Warsaw 27 Aug '12

27 Aug '12

On Aug 21, 2012, at 01:04 PM, Stephen J. Turnbull wrote: >Patrick Ben Koetter writes: > > > They have free accounts for open source projects. It might be a > > nice way to organize a translation community. > >It's likely that we don't have to organize one, we already have one. >Barry, why don't you try to get in touch with that Vietnamese lady and >see what she thinks? Right, that would be Clytie, CC'd here. However, it's been a while since we've heard from her. >There are also active translation communities at Debian and Launchpad, >and I would assume at Red Hat/Fedora. Both Deb and Ubuntu are happy >Mailman users, and I would guess Red Hat/Fedora, too. All probably >would find some of the MM3 features very attractive for their own use. Definitely, and I've looked at all of the various translation services, mostly from the point of view of a project manager non-translator. E.g. how would I push updates into the service, how would I pull updates from the service, etc. I think I have a fairly good sense of what will work and what will cause headaches. I think I've posted to mailman-i18n@ before about my thoughts there. I'm CC'ing that list here too. But in some sense, it's more important for the translators to feel comfortable and welcome in whatever system we chose. Most are non-technical, so I think it's easier for us to make project workflow conform to a great translation system's quirks (and there *will* be quirks ;) than for them to work around pain in a translation system that easily integrates with our workflow. One question I have, and Steve, you're probably a great person to weigh in on this: what requirements does the GPLv3+ and being a GNU project place on us? Cheers, -Barry

3 2