I'm happy to announce that a new service launched beta testing on Drupal.org under http://localize.drupal.org/ to help translation teams involve more people and reach new heights in the level of Drupal.org project translations. This central web based translation service is about to step in place of generating translation templates manually, committing them to CVS and releasing them with projects waiting for teams to picking them up and then committing translations on their behalf from the perspective of the module and theme maintainers.

This centralized service already helps module and theme developers by automatically parsing all release source codes posted on Drupal.org slightly after they are published, and helps translation teams by easing sharing work among contributed modules. While we have almost 5000 projects with releases, the total number of translatable strings is "only" above 147000, "just" 40 times the strings found in Drupal core. There is lots of repetition and similar content of which this central service provides oversight for translators. Drupal site owners using the Localization client tool can contribute to translations on Drupal.org directly from the convenience of their website.

Localize.drupal.org is also set to help users with an install profile which will integrate with this service and download and update translations when requested from packages hosted on the server. This side of the service is still in its specification phases, so do not expect immediate results.

However, ten of the localization teams already migrated to localize.drupal.org, so the early adopters include Croatian; Czech; Dutch; Hindi; Japanese; Lithuanian; Norwegian Bokmål; Norwegian Nynorsk; Telugu and Portuguese, Portugal. It is very easy to join these translation teams, since your Drupal.org user account works in a single-sign-on system with localize.drupal.org, so you don't need to register a new user account at all.

Those interested in more details of the service are welcome at the Drupalcon Paris session titled "Here comes localize.drupal.org" on September 2nd. Those interested in contributing to the infrastructure under this service, your help is most useful in the Localization server issue queue, where you can help write tests for the module (which ensures easier feature deployment and performance changes in the future) as well as fixing any outstanding performance concerns.

Comments

Cool. I attended the presentation in Barcelona two years ago, and was totally intrigued by this plan, and now it is here :)
Guess Drupal in kizuaheli is near...

May we get rid of the translations subdirectory in our projects? Do we have to migrate these to l.d.o.?

What do we need to know? Where do we find information about it?

Thanks, Gábor. Great job! :)

the translations subdirectory still remains until the remaining issues are not fixed.
the migration should be the responsibility of the translation teams, not module maintainers..

more info:
http://hojtsy.hu/blog/2009-jul-30/localizedrupalorg-come-life-so-what-ab...

status:
http://drupal.org/project/issues/search/drupal?issue_tags=ldodomination

Hi,

Great choice you guys made with Gettext.
We use this in our applications for quiet some years now and it works like a charm.

Suggestion: sometimes you need your .po translations in Javascript also; you could make a function _() (as in php) to do your translations with the same Gettext-functionality

We also made an application for creating these .po / .mo files on the run ; if interested we'll share it with the community.

Keep on the good work

Translating strings in JavaScript:
http://drupal.org/node/323109

extract translations into .po file:
http://drupal.org/project/potx