Finished translations do not reset "Outdated translation" attribute

+++ b/sources/node/tmgmt_node.moduleundefined
@@ -44,5 +44,11 @@ function tmgmt_node_update_node_translation($node, $data, $language) {
   tmgmt_field_populate_entity($node, $language, $data);
+  //reset translation field, which determines outdated status
+  $node->translation['status'] = 0;
+  //source node; mark its translated friends as up to date
+  if(isset($node->nid) && $node->nid == $node->tnid){
+    $node->translation['retranslate'] = 0;

Make sure the comments follow the coding standard, which means a space after //, start with an upper case character and end with a "."

This has one problem. That is, if the source node has changed again, it has the chance of incorrectly changing the flag.

Can we make this configurable? Add an if (variable_get('tmgmt_node_update_status', TRUE) and add a hook_form_alter for http://api.worldempire.ch/api/tmgmt/ui%21includes%21tmgmt_ui.pages.inc/f... in tmgmt_node_ui module, adding checkbox, there are already a few examples there.

Consider this list of events:

- New job created to translate node X to DE
- node X is changed, translations are marked as needing re-translation.
- Original translation comes back, DE node is marked as translation updated.

Also related to #1623402: Option to cancel pending translation jobs when its source content is edited. Not sure how to deal with this.

#4: tmgmt-reset-outdated-attribute-1619786-1.patch queued for re-testing.

Commited, better than not having it I think, we can deal with conflict situations in case they occcur.