Our last major update to localize.drupal.org was about two months ago, bringing in a whole new user interface for translation and easier navigation and collaboration. Since that was a big user interface change and needed some time to settle, I switched gears to work on the backend of the system. The ultimate goal is to get our main backend module called Localization server as general purpose as possible.
Many people noticed that the software on localize.drupal.org would be nice to use for translation of other projects so generalizing the software to get in more collaborators and contributors was a logical step. The 6.x-2.x-beta2 version of the module was released earlier this month with a blog post explaining its general use titled Using Drupal as a collaborative software translation tool. This new release included some pretty big architectural changes, rebasing the module on l10n_server and starting to separate the database backend, the Drupal specific connectors and the exporters more.
There is still quite some work to do around there, but it was time to make the jump and roll out this new backend on localize.drupal.org as well. This time the rollout went well if you do not notice any changes. While there were minimal UI fixes as well, generally nothing should have changed on the front end. However, the backend now provides more tools to administer the server, so in case of the parsing errors we occasionally notice for example, we can easily reset a release for parsing again on the user interface.
Let us know if you notice any new problems. See the having issues page for explanation on how and where to submit bug reports. Thanks!
Comments
All my thanks Gábor
All my thanks Gábor for the huge efforts you're doing for the Drupal community
This sounds great Gabor,
This sounds great Gabor, looks like we are moving in the right direction.
I really have some catch up to do, I'll be testing this one in the next weeks and report back.
At this point, what do you think of an install profile like 'Crowd translation' (Set up a translation server for other OSS projects)?
oh, yeah
Yes, the idea is that we should be able to pull together an install profile. I've also built the Curie theme (http://drupal.org/project/curie) to serve as a base for this install profile unless we get better more application focused themes. I did not find general purpose web app focused themes.
I think we still need some cleanup in l10n_server, like making the exports more modular. Currently, the exports are still Drupal based, but should not be by default.