Looking for the coordinator of zh_cn mailmani18n.
Hi,I'm new here.I just want to translate mailman into Chinese(Simplified),so I'm looking for Leona (http://wiki.list.org/display/DEV/Languages) Thanks. Best Regards, Christopher Meng------'Cicku' Ambassador/Contributor of Fedora Project and Contributor of GNU. Blog:http://cicku.me Twitter:@cickumqt Hope you can visit and leave some comments. More Contact info see here:http://about.me/cicku
On Apr 28, 2012, at 12:55 PM, Christopher Meng wrote:
Hi,I'm new here.I just want to translate mailman into Chinese(Simplified),so I'm looking for Leona (http://wiki.list.org/display/DEV/Languages)
We currently don't have a very good translation story for Mailman 3. While all the good coding standards are still in place (i.e. translated template lookup, gettext style strings in source code), what is missing is extraction and uploading of catalogs, downloading language packs, etc. Unfortunately, this is not something I have time to work on right now. Maybe someone in the mailman-i18n community can take a look at our options, the pluses and minuses, and give us a report. Here are the options I know about: - Launchpad translations. Pros: free software, project already hosted there. Cons: our source tree layout isn't compatible with their model, and I'm not sure how to handle our templates. - Transifex.net. Pros: open source, demo looked very nice at Pycon, has an API that may integrate better with our workflow. Cons (maybe): Unsure of the best way to utilize the site, how many translators do they have? - translatewiki.net. Pros: open source (I think), had some discussion with their developers back in January. Cons: is wiki a good fit for translating Mailman? May have some problems ensuring FSF requirements for contributions. - Pootle and similar. Cons: I really don't want *us* running any translation service; too hard to babysit based on our resources. What else is out there? -Barry
Hi, On Sat, Apr 28, 2012 at 21:50, Barry Warsaw <barry@python.org> wrote:
- translatewiki.net. Pros: open source (I think),
GPLv2 or later. But a lot of what you get by using TWN is not in the software itself, but in the community and staff that exists on the site. If you run your own copy you won't necessarily get the same kind of community and staff to go with it.
had some discussion with their developers back in January. Cons: is wiki a good fit for translating Mailman?
Why not? ;) I don't do any translation myself and have only used the interface for ~5 mins over a month ago so read with grains of salt. (i.e. I may be saying something false or wrong) It is a wiki and the strings are stored as wiki pages. It might be possible to edit those strings as individual wiki pages, I'm not sure. But there's an ajaxy, dynamic interface for translators and surely the vast majority of online translations use that. (there's also the option to download strings in bulk and do translations with an offline tool and then automatically import them to the wiki. but online translation is preferred to offline and I think is more commonly used. anyway, if for some reason a particular user doesn't like the web interface they might be able to continue using the same tools they use now for the actual translation, just the checkout/checkin process would be different) You should talk to some of the existing users of TWN directly to see about their experience with it and get some of the existing mailman translators to try it out with any project that already uses TWN. (just register and do some translations for an hour)
May have some problems ensuring FSF requirements for contributions.
I discussed this with the FSF again on Tuesday (6 days ago). There's been some progress off and on with getting the FSF to approve the use of TWN. Was stalled recently because there were other things distracting them but now they're working on it again. I should have another update from them within ~8 days from now. -Jeremy
On Apr 30, 2012, at 05:23 PM, Jeremy Baron wrote:
On Sat, Apr 28, 2012 at 21:50, Barry Warsaw <barry@python.org> wrote:
- translatewiki.net. Pros: open source (I think),
GPLv2 or later. But a lot of what you get by using TWN is not in the software itself, but in the community and staff that exists on the site. If you run your own copy you won't necessarily get the same kind of community and staff to go with it.
We definitely don't want to run our own service IMO. However, the code that the service we use does need to be free software or at least open source.
had some discussion with their developers back in January. Cons: is wiki a good fit for translating Mailman?
Why not? ;)
Honestly, since I don't do translations I don't know either, that's why I'm looking for input. :) Ideally, the system would be as inviting, open, and easy to use as possible for translators, but also not be painful for the developers who need to upload pot files and templates, and download .po files and translated templates on our own schedule. One nice thing about transifex IIUC, is that it has an API that we could hook up to our release scripts. So we can upload and download from the command line, which would be fantastic. I've never tried it though.
You should talk to some of the existing users of TWN directly to see about their experience with it and get some of the existing mailman translators to try it out with any project that already uses TWN. (just register and do some translations for an hour)
I'd love to get some feedback from folks on this list. Any translators here have an opinion?
May have some problems ensuring FSF requirements for contributions.
I discussed this with the FSF again on Tuesday (6 days ago). There's been some progress off and on with getting the FSF to approve the use of TWN. Was stalled recently because there were other things distracting them but now they're working on it again. I should have another update from them within ~8 days from now.
Cool! -Barry
participants (3)
-
Barry Warsaw -
Christopher Meng -
Jeremy Baron