Google MT Connector: Difference between revisions

From Okapi Framework
Jump to navigation Jump to search
No edit summary
 
m (1 revision imported)
(No difference)

Revision as of 19:19, 4 June 2016

Overview

Note: Please, note that this API is no longer available and that Google has replaced it with a paid version]. The new Google MT v2 Connector is available for users who wish to use the paid service provided through the version 2 of the API.

Possible alternatives:

Google offers a well-known MT engine: Google Translate. The framework provides a connector for the Google Translate v1 API. You can find more information about Google MT here: http://code.google.com/apis/ajaxlanguage.

The engine supports inline codes.

This connector accesses a remote server and makes your source text available to Google, but no corresponding translation is sent to Google. You must also respect Google's Terms of Service to use it.

Parameters

This connector has no parameters.

Limitations

  • In some cases you may have results with more inline codes than in the original source. For example when a phrase in bold is translated into two separate parts: both parts may get enclosed with the inline codes that were corresponding to the initial bold. While this is not a limitation on itself, it may result in issues if the codes are not clonable.
  • Depending on the volume of data you are processing you may intermittently be blocked from using Google Translate. See the GTT Batch Translation Step for another way to access Google MT system.