Hi, In Hong Kong there will be a design summit session to discuss translation tools: http://summit.openstack.org/cfp/details/169
From our last round of evaluating tools, Pootle was a close second to Transifex:
https://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-ErDUdFgzT3VNVXQxd095bFg... To help make the design summit more productive, I have set up a simple test Pootle server so that we can examine it and answer any questions we might have before the design summit. You can log into the test server here: http://translate-dev.openstack.org/ I have done very little configuration of the system, I just wanted to get something up quickly for people to look at. I have imported nova, horizon, and openstack_dashboard as projects. Note that if you look at nova, the number of translated strings Pootle reports is less than transifex -- that's because Pootle has marked all of the fuzzy-matched strings as "needs work", and strings that "need work" don't count as being fully translated. One thing that I believed has changed since the last time we looked at Pootle is translation memory. Here are the current docs: http://docs.translatehouse.org/projects/pootle/en/latest/features/translatio... Since that describes how it uses an external translation memory populated with open source software by default, I believe that also means that Pootle's performance in the "crowdsource" category may have improved as well. I'm also optimistic about the integration with Git. Here's the documentation: http://docs.translatehouse.org/projects/pootle/en/latest/features/version_co... It looks like we may have options for getting nice git commits out of this; it says a typical git commit message looks like this: Commit from GNOME Pootle by user Sipho. 80 of 100 messages translated (7 fuzzy). Also, from what I've seen, it should not be very difficult to integrate Pootle into the project infrastructure -- the deployment is fairly simple. Keep in mind this isn't a fully-formed proposal for a new system -- just a test server running a basic configuration so we can look into it and discuss it more at the Summit. Please feel free to log into the test server and play with it. After you log in, just let me know if you would like me to make your user an admin. -Jim
Thank you, James. The test server is very helpful for evaluation and test. Can you make me as an admin? I'd like to try more functions. Regards Ying Chun Guo (Daisy) jeblair@openstack.org (James E. Blair) wrote on 2013/10/11 00:22:11:
Le 10/10/13 18:22, James E. Blair a écrit :
Hello, I noticed you have listed TranslateWiki there, I took the liberty to forward your email to their team :-] I am sure some of the drawback you have listed there could get a better reply from them, hence I forwarded them your email. Documentation for new projects is: https://translatewiki.net/wiki/Translating:New_project You can get in touch with them on #mediawiki-i18n :-] It would be really nice to have OpenStack join the translatewiki community. It has a very strong community even in the most "exotic" languages :-) -- Antoine "hashar" Musso
On 10/10/2013 09:22 AM, James E. Blair wrote:
It looks like the system works, I signed up for it too :) One of the needs from the i18n team is reporting on people's activity. Is there a way to retrieve the translator stats for a project in pootle? For example, find how many words each translator translated in a certain project.
That feature looks really good to me: I found interesting suggestions in the Italian translations.
Does this mean that translators will be directly recognized as Authors in git commit logs or will we need to do some parsing for them to show up on activity.openstack.org? /stef -- Ask and answer questions on https://ask.openstack.org
My message http://lists.openstack.org/pipermail/openstack-infra/2013-October/000341.htm... was probably not seen on openstack-i18n. :) Just a couple info below. Stefano Maffulli, 17/10/2013 03:05:
translatewiki.net has translation memory too (since a few years; Pootle's is in preliminary stage if I read their docs correctly).
translatewiki.net does this. Nemo
participants (6)
-
Antoine Musso
-
Clark Boylan
-
Federico Leva (Nemo)
-
jeblair@openstack.org
-
Stefano Maffulli
-
Ying Chun Guo