Add a Translation Management server component. This will allow Translators / Translation service providers to use Drupal as a Management system to get translation jobs from other Drupal instances and do the translation work in their own system. With even a small distribution, this product is a few clicks away for end users!

This task has been submitted as GSoC project:
http://groups.drupal.org/node/222909

I'm not sure if we should plan to do the service implementation even in a separate project. It might be a pretty big piece of software that doesn't affect plain client systems at all. At least the project should be implemented in a separate repo until completion.

Comments

fubhy’s picture

fubhy commented

It should be a separate project... definitely! It will also be really interesting to figure out which parts of the local translator ui can be moved into this component. We can probably merge all of the local translator stuff over to the server project.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

I've discussed this quite a bit already with fubhy. I agree that this should be a separate project.

Problem is, if we move the local translator UI to the server, then there is no local translator left :p And if we keep it in the main project and make it a re-usable as possible, then we need to depend on the main project. Which is less of a problem, in my opinion.

I'm sure we'll figure something out. First step is finishing a first, working iteration of the local translator.

fubhy’s picture

fubhy commented

I agree that we need to finish the local translator first and make it really cool!

However, the server will have a full blown UI for managing translations (this will truely kick ass!). We can make it so that there are two translator plugins (one for actual communication with REMOTE instances of the TMGMT Server component and one for local communication with the TMGMT Server component). The Local Translator UI will already cover some of these aspects so we can probably re-use a lot of the code from that and eventually even deprecate the Local Translator UI in favor of that functionality. However, this is not the right place for this discussion :). Let's first finish the Local Translator UI.

Edit: Oh and... Depending on the main TMGMT project is probably not such a good idea as that would add all the entities from the main project and all the other things (which would not be needed) to the server environment.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Re the edit: If we can manage to separate the local translator UI from the tmgmt base *module* (not project), then you don't have to install tmgmt.module on the server, but it could still live within this project. Imagine the following module structure:

- User translator (UI) (no dependency on tmgmt)
- Local translator (depends on user translator and tmgmt)
- Remote/Client translator (integrates with translator server, depends on tmgmt)

That could all live within the tmgmt project, then we have as a separate project:

- Translator server (depends on user translator (UI))

Ok, enough of that, back to step #1. local translator with integrated UI.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Project: Translation Management Tool » Translation Management Server Sandbox
Version: 7.x-1.x-dev »

Moving this over to the server sandbox.