grobot authored Mar 20, 2013 and Sascha Grossenbacher committed Mar 20, 2013

Issue #1649364 by grobot, Staratel: Fixed all languages show as 'unsupported' - access token failure due to POST encoding .

German Martin authored Jun 05, 2012 and Sascha Grossenbacher committed Jun 05, 2012

Issue #1574516 by GDrupal: Fixed Microsoft translator removed support for Bing ID, requires access token now.

Issue #1491550: Merge the translation property into the data property on the job item entity and clean up of entity and node source tests.

Issue #1442366 by fubhy: Change the canTranslate method to also accept the translator entity as an argument and apply that pattern to the various functions that use that method.

Please forgive me for that last commit. It might actually be good to check for the availability right there. Although thtat means that we might have that check twice in some cases.

Major cleanup and rewrite. Source and translation controllers have been split up into a UI and a Plugin controller. We also support other controllers now. There already is a views controller, but it doesn't do much right now.

Job item and job state transitions are partly working now. Job messages still need to be changed to better support job item state transitions. Patch for that is incoming too.

Replaced isNeedsReview/needsReview()/accepted() calls on jobs with corresponding job item calls to fix some tests.

canTranslate on the microsoft translator now checks for the length of each text before sending it to microsoft. However, we still need to find a way to display error messages to the user when a job is not translatable.

getSupportedTargetLanguages now caches its output in the translator entity and updates that cache on __destruct(). Furthermore, we now have a configure link on the modules page for the tmgmt core module when the ui submodule is enabled. Also, getSupportedLanguages has been deleted.