translation

Deleted as it is considered as to be "too long and rambling".
Will be published elsewhere ....

Analog to 'Node Source' there is an 'Entity Sources' listing on which you can manage bulk translation with entities.

Go to Administration > Configuration > Regional and language > Translation Management > Entity Sources. Here you can access all entity types that have been marked as translatable. In the case below 'Comment' and 'Node'.

In this case we want to translate entites with 2 different source languages. Therefore 2 seperate jobs will be created. The need to be submitted to translator in sequence. With the first job the the button will say 'Submit to translator and continue' to indicate that there are more jobs to take care of.

The rest of the process works the same as in the previous cases.

Administration > Configuration > Regional and language > Translation Management > Jobs provides a good overview of all pending jobs.

The jobs and items are color coded:

A pie chart represents the items included in the job as well as the prgress that has been made so far.

From here you can execute mass operations by marking jobs with the check box and then choose an appropriate operation. Click the 'execute' button for execution.

By clicking on the 'manage' link in a job you will get the details of a job.

From here you can start activities on job items.

Good to know: You can override the default label after having requested the job and give it a name with a meaning. That can be very helpful when managing several translation jobs.

The node source view provides a tool to mark several node for translation. You will find it at Administration > Configuration > Regional and language > Translation Management > Node Source.

The little color boxes indicate the status of the translation process. When rolling over a box with the mouse you are presented with the corresponding status in text.

Step 1

Choose the nodes you want to translate. Use the exposed filters at the top of the page or do it manually. Choose 'Request Translation'

Step 2

For each source language in the chosen nodes you will be presented with a seperate window. Choose the target language and the translator you want to use. There will be one job for each source language.

To see the progress graphs you will need to download and activate Google Chart Tools.

Use the 'Submit to translator' button to start the process. Or save the job for later submission. When submitted, a new job is created with one item or each target language.

The following rules export is an example that translates all articles which are not already german or undefined to german using translator called test_translator (Microsoft in this case, but any translator that supports automated checkout should work).


{ "rules_auto_translate_with_microsoft" : {
"LABEL" : "Auto-Translate with Microsoft to German",
"PLUGIN" : "reaction rule",
"REQUIRES" : [ "rules", "tmgmt" ],
"ON" : [ "node_insert", "node_update" ],
"IF" : [
{ "node_is_of_type" : { "node" : [ "node" ], "type" : { "value" : { "article" : "article" } } } },
{ "NOT data_is" : {
"data" : [ "node:language" ],
"op" : "IN",
"value" : { "value" : { "und" : "und", "de" : "de" } }
}
}
],
"DO" : [
{ "tmgmt_rules_create_job" : {
"USING" : { "source_language" : [ "node:language" ] },
"PROVIDE" : { "job" : { "job" : "Job" } }
}
},
{ "tmgmt_rules_job_add_item" : {
"job" : [ "job" ],
"plugin" : "node",
"item_type" : "node",
"item_id" : [ "node:nid" ]
}
},
{ "data_set" : { "data" : [ "job:target-language" ], "value" : "de" } },
{ "data_set" : { "data" : [ "job:translator" ], "value" : "test_translator" } },

This is a tutorial showing how to integrate user-defined flags with the views provided by TMGMT. For this example, we are showing the use case of flagging as "ready for translation". This could be useful if your workflow requires a review process of the source content before submitting for translation.

1. Create your custom flag. Important options: Global flag: checked (ensures a node is globally flagged, not dependent on the user viewing), Flag translations of content as a group: selected (ensures that translated nodes are linked to the source node).
2. Set Flaggable content to Article and/or your content types.
3. Clone or directly edit the existing view named "Node Source Overview". If cloning: click edit for that view under Operations. On the next page, click the drop down arrow next to "edit view name/description" and select "clone view". Name it and save it.
4. Under "Page settings", set a new path if you cloned the view. Optionally change the title and tab structure by clicking "Tab:Node source..."